7.0
Table Of Contents
- Reference Architecture
- Contents
- vRealize Automation Reference Architecture Guide
- Updated Information
- New Features in vRealize Automation Since Release 6.2
- Initial Deployment and Configuration Recommendations
- vRealize Automation Deployment
- vRealize Business Standard Edition Deployment Considerations
- vRealize Automation Scalability
- vRealize Business Standard Edition Scalability
- vRealize Automation High Availability Configuration Considerations
- vRealize Business Standard Edition High Availability Considerations
- vRealize Automation Hardware Specifications
- vRealize Automation Small Deployment Requirements
- vRealize Automation Medium Deployment Requirements
- vRealize Automation Large Deployment Requirements
vRealize Automation Scalability 5
Consider all applicable scalability factors when configuring your vRealize Automation system.
Users
The vRealize Automation appliance is configured for syncing less than 100,000 users. If you need to sync
more than 100,000 users, increase the appliance memory by 2 GB.
Concurrent Provisions Scalability
By default, vRealize Automation processes only two concurrent provisions per endpoint. For information
about increasing this limit, see Configuring vRealize Automation.
VMware recommends that all deployments start with at least two DEM-Workers. In 6.x each DEM-Worker
could process 15 workflows concurrently. This has been increased to 30 in 7.0.
If machines are being customized through Workflow Stubs, you should have 1 DEM-Worker per 20
Machines that will be provisioned concurrently. For example, a system supporting 100 concurrent
provisions should have a minimum of 5 DEM-Workers.
For more information on DEM-Workers and scalability see Distributed Execution Manager Performance
Analysis and Tuning
Data Collection Scalability
Data collection completion time depends on the compute resource capacity, the number of machines on
the compute resource or endpoint, the current system, and network load, among other variables. The
performance scales at a different rate for different types of data collection.
Each type of data collection has a default interval that you can override or modify. Infrastructure
administrators can manually initiate data collection for infrastructure source endpoints. Fabric
administrators can manually initiate data collection for compute resources. The following values are the
default intervals for data collection.
VMware, Inc.
12