This is a general discussion of scalability considerations for vWorkspace.
The following guidelines are provided as a conservative indication of the number of virtual desktops that should be managed through vWorkspace Connection Brokers and Farms. Note that these are not hard limits, and depending on the frequency that users log on and off then higher scalability is very achievable.
For a recent study of scalability in vWorkspace see http://www.quest.com/documents/landing.aspx?id=14974.
Also, please note that these limits are for a VDI deployment of virtual desktops hosted on a hypervisor. For Session Host (Terminal Server)-based deployments, the load on each Connection Broker is lighter because it only needs to maintain status information on each Session Host and not each virtual desktop. A rough guideline is that one Connection Broker is required for every 3000-5000 sessions, depending on logon frequency, with a spare recommended for redundancy.
Virtual desktops managed per Connection Broker: 5000
Total virtual desktops per vWorkspace farm: 25000
Total Connection Brokers per farm: 20
There are other scalability limits to consider from other vendors - especially the hypervisor management servers:
For large farms, multiple vCenter Servers and SCVMM servers will be required. It is recommended to break virtual desktops into groups of 2000 so that they can be distributed across the vCenter/SCVMM instances effectively.
For more notes on Hyper-V scalability, the following Microsoft paper is recommended: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=bd24503e-b8b7-4b5b-9a86-af03ac5332c8
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center