Giving continuity to my VMware View Limits and Maximums series (VMware View 4.0 | VMware View 5.0) I am now releasing an updated version for Horizon View 5.2.
As an administrator or architect you should always make sure that your design sizing’s are within the product’s Maximums and Limits in order to be entitled to VMware Support.
Horizon View 5.2 introduced many new features and improvements, including a more scalable architecture that now supports 10,000 desktops using a single vCenter Server (I’ll soon post an article about ups and down for single vCenter architecture).
The scalability improvements introduced in Horizon View 5.2 come from four very important features: Multi-Network Support, Accelerated View Admin Performance, Space Efficient Disk Utilization and support for 32 host clusters when using NFS or VMFS. Read more about the new Horizon View 5.2 features in What’s New in Horizon View 5.2 (beyond Marketing).
The limits may vary according to the releases in use. The limits in this post are specific to Horizon View 5.2 and vCenter Server 5.1. The comparisons are against limits published with VMware View 5.1
· 32 Hosts per Cluster when used with VMFS – changed from 8 Hosts per Cluster
· 32 Hosts per Cluster when used with NFS – did not change
· 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.
· 10,000 VMs per vCenter – changed from 2,000 VMs per vCenter
VMware is now officially supporting 10,000 virtual desktops per vCenter Server, installable or appliance. This is a major architectural change and should drastically reduce View pod footprint and enables easier backup and DR for the entire solution.
· 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
· Total HTML 5 connections per pod, 256 (To be Confirmed) – New Limit
This is a new limit for connections coming via HTML5 protocol.
I find amusing to identify how and when each component of the overall solution was improved or upgraded. The table below demonstrate when each component was upgraded and what is the new limit.
This article was first published by Andre Leibovici (@andreleibovici) at myvirtualcloud.net.