Operational Defect Database
BugZero updated this defect 47 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 67354
VMware App Volumes Sizing Limits and Recommendations
Last update date:
4/2/2024
Affected products:
App Volumes
Affected releases:
2.x4.x
Fixed releases:
No fixed releases provided.
Description:
Details
This article provides sizing limits and recommendations for a VMware App Volumes 2.xFor App Volumes 4, please see VMware Configuration Maximums. For Horizon limits see VMware Horizon sizing limits and recommendations, see KB 2150348 For additional detail please see the following TechZone articles: VMware App Volumes Database Best PracticesApp Volumes Architecture
Solution
App Volumes Manager (AVM) Server Sizing If you have a large number of concurrent logins (such as many users simultaneously logging in at the beginning of a shift) will put a greater demand onthe App Volumes Manager servers. When deciding how to size and scale your environment consider the number of concurrent logins per second required.Each AVM has been tested for 2,000 concurrent logins at a one-per-second login rate. Concurrent Logins <=2,000 2,000 to 5,000 5,000 to 7,500 >7,500 AVMs per POD2344+1 for every 2,500 usersCPUs on each AVM4688RAM on each AVM4 GB8 GB16 GB16 GBvCenters per POD (1 per resource block)2344+1 for every 2,000 VMsChanges to Manager\clock.yml Servers:4 workers:2 Servers:6 Workers:2 (Default) Servers:8 Workers:2 Servers:8 Workers:2 Logins per second (tested)*2/second3/second4/second4/s +1 for each AVM * Delay writable creation for group/OU members until they log in option requires additional time to create volumes. When using this option, the user’s first login is tested at a rate of 1 login per 8 seconds. vSphere Sizing Virtual Machine density will affect the performance of an App Volumes implementation. VMware performance testing demonstrates optimal performance using the following maximum VM density. Virtual Machines per ESX host110 tested*Virtual Machine guest configuration2 vCPU, 4 GB RAMVirtual Machines per vCenter2,000 tested Storage Limits AppStacks per VM5 tested* No more than 8-10 recommended*** No. of user Mounts per AppStack(VMDK) 1000 per VMFS datastore tested** 2000 with vSAN tested No.of UWS per Datastore 1000 per VMFS datastore tested** 2000 with vSAN tested * = VMC testing Hardware: Dual Intel Xeon E5-2686 v4(18 core 2.3GHz, 2.7GHz All Core Turbo).** = Storage group on VMFS is used to achieve a larger scale.*** = When using the App Volumes 2.x agent, the number of AppStacks directly impacts login and application performance. Results per environment may vary as hardware/software configuration and application complexity will affect system performance and limits. In order to reduce the number of AppStacks VMware recommends creating logical groups of applications into fewer AppStacks to achieve better performance. Alternatively, App Volumes 4 provides better support for packaging applications individually.
