We have one OPSI server and about 300 client computers in our LAN.
The main usage of our OPSI server is deploying software to the workstations. Mostly it’s multicast deploying (20 workstation at the same time). But if it's possible we would like to deploy several big packages to 100 workstation at the same time.
We deploy a lot of CAD’s and Graphics software (like a Revit, AutoCAD, 3ds Max, ArchiCAD, Photoshop). Average size of one software package is about 3Gb. Sometimes it's required to deploy 5-10 packages for each workstation at the same time.
Workstations have 1Gb/s connection to the switches. Switches have 10Gb/s connection to each other.
Main workstation configuration is 8700K (3.7Ghz/4.7Ghz, 6cores/12 threads), 32Gb 3200MHz, ssd, 1Gb/s LAN connection.
What is optimal hardware requirements for OPSI server in such case?
CPU
1. What is workload on the CPU during deploying?
2. What is more important for OPSI server CPU during deploying? Core and threads? Or CPU frequency? Does OPSI use multi-threading?
RAM
3. How much RAM does OPSI server need? Does OPSI server use RAM cache for multicast deploying?
DISK
4. What is performance dependence of OPSI server disk system?
5. How could RAID 5 array improve performance in comparison of single 7200 RPM disk?
NETWORK
6. What is performance dependence of OPSI server LAN connection speed? How could 10Gb/s LAN connection of OPSI server improve performance in comparison of 1Gb/s LAN connection?
OPSI server hardware workload
-
uncle_scrooge
- Beiträge: 650
- Registriert: 21 Feb 2012, 12:03
- Wohnort: Mainz
Re: OPSI server hardware workload
Might be only the wrong wording. But to make it clear: OPSI does no multicast.
And, when it comes to deploying packages, we are talking of SAMBA. OPSI 'only' handles the administrative tasks.
So you want to tune your SAMBA daemon for speed.
CPU:
Any modern processor should be sufficient. And no, afaik, OPSI does no multi-threading.
RAM:
For your configuration 32GB should be (more than) sufficient.
Disk:
In general: The faster the better.
As said before, for deployment SAMBA comes into play. Which has to read a lot of data.
RAID5 gives a slightly better read performance than a single disk. But I would go with a RAID1. And SSD. Aren't that expensive nowadays.
Network:
It's simple maths. If you deploy only one package to a client at a time there is no performance gain. But when you deploy a couple of clients in parallel, it's more fun with a thicker pipe.
Depends a bit on the used NIC. A cheap RealTek chip will stress the CPU and slow things down. But a 'server grade' card will do a lot of offloading, and keep the pipe saturated.
And, when it comes to deploying packages, we are talking of SAMBA. OPSI 'only' handles the administrative tasks.
So you want to tune your SAMBA daemon for speed.
CPU:
Any modern processor should be sufficient. And no, afaik, OPSI does no multi-threading.
RAM:
For your configuration 32GB should be (more than) sufficient.
Disk:
In general: The faster the better.
As said before, for deployment SAMBA comes into play. Which has to read a lot of data.
RAID5 gives a slightly better read performance than a single disk. But I would go with a RAID1. And SSD. Aren't that expensive nowadays.
Network:
It's simple maths. If you deploy only one package to a client at a time there is no performance gain. But when you deploy a couple of clients in parallel, it's more fun with a thicker pipe.
Depends a bit on the used NIC. A cheap RealTek chip will stress the CPU and slow things down. But a 'server grade' card will do a lot of offloading, and keep the pipe saturated.