As an administrator or architect you should always make sure that your sizing’s are within VMware View Maximums and Limits in order to be entitled to VMware Support.
VMware View 5.1 introduced many new features and improvements, however this release is not particularly focused on scalability from a maximum and limits perspective. The scalability improvements introduced in View 5.1 come from three very important features: View Storage Accelerator (CBRC), View Composer Array Integration, and support for 32 host clusters when using NFS. Read more about the new VMware View 5.1 features in What’s New in VMware View 5.1 (beyond Marketing).
The limits may vary according to the releases in use. The limits in this post are specific to VMware View 5.1, View Composer 3.0 and vCenter Server 5. The comparisons are against limits published with VMware View 5.0
· 8 Hosts per Cluster when used with VMFS – did not change
This limit is hard-coded in View Composer; however it comes from a VMFS limitation on the number of hosts that can simultaneously read from a single VMDK. This VMDK in a VMware View environment with View Composer would be the Replica disk.
· 32 Hosts per Cluster when used with NFS – changed from 8 Hosts per Cluster
· 16 VM’s per CPU core – did not change
· 1,000 VMs per View Composer desktop pool or replica – did not change
· 140 VMs per LUN with VAAI support – did not change
Without VAAI support the recommended number is still 64 VMs per LUN. This limit comes from the number of SCSI LUN reservations caused by VM metadata updates. With VAAI the reservation happens at the VMDK level.
· 2,000 VMs per vCenter – did not change
Despite the limit above I recommend you to keep this number at around 1,500 desktops and observe vCenter response times as you scale up to 2,000. VMware View generates a large amount of operations (power on and off, reconfiguration, cloning, snaps) that consume vCenter resources.
· 1000 VMs per host – did not change
This limit is established by vSphere 5, not VMware View.
Maximum Number of Connections
· 1 Connection Server with Direct connection, RDP, Tunneled or PCoIP, 2,000 – did not change
· 7 Connection Servers (5+2 spares) Direct connection, RDP or PCoIP, 10,000 – did not change
· 1 Connection Server with PCoIP Secure Gateway, 2,000 – did not change
I find very amusing to identify how and when each component of the overall solution is improved or upgraded. The table below demonstrate when each component was upgraded and what is the new limit.