Technical data
Solution Architectural Overview
VMware Horizon View 5.3 and VMware vSphere for up to 2,000 Virtual
Desktops Enabled by Brocade Network Fabrics, EMC VNX, and EMC Next-
Generation Backup
73
Server configuration guidelines
When designing and ordering the compute/server layer of the VSPEX
solution described below, several factors might alter the final purchase.
From a virtualization perspective, if a system’s workload is well understood,
features like Memory Ballooning and Transparent Page Sharing can
reduce the aggregate memory requirement.
If the virtual machine pool does not have a high level of peak or
concurrent usage, the number of vCPUs can be reduced. Conversely, if
the applications being deployed are highly computational in nature, the
number of CPUs and memory purchased might need to be increased.
Table 9 identifies the server hardware and the configurations used in this
solution.
Table 9. Server hardware
Servers for virtual
desktops
Configuration
CPU:
1 vCPU per desktop (8 desktops per core)
63 cores across all servers for 500 virtual desktops
125 cores across all servers for 1000 virtual
desktops
250 cores across all servers for 2000 virtual
desktops
Memory:
2 GB RAM per virtual machine
1 TB RAM across all servers for 500 virtual desktops
2 TB RAM across all servers for 1,000 virtual
desktops
4 TB RAM across all servers for 2,000 virtual
machines
2 GB RAM reservation per vSphere host
Network
6 x 1 GbE NICs per server for 500 virtual desktops
3 x 10 GbE NICs per blade chassis or 6 x 1 GbE
NICs per standalone server for 1,000 virtual
desktops
3 x 10 GbE NICs per blade chassis or 6 x 1 GbE
NICs per standalone server for 2,000 virtual
desktops
Notes:
Add CPU and RAM as needed for the VMware vShield Endpoint and Avamar
components. Refer to the vendor documentation for details concerning
vShield Endpoint and Avamar resource requirements.
To implement VMware vSphere High Availability (HA) and to meet the listed
minimum requirements, the infrastructure should have one additional server.
Overview