7.1

2 Locate the binding name and readerQuotas lines in the le.
<binding name=”ProxyAgentServiceBinding” maxReceivedMessageSize=”13107200”>
<readerQuotas maxStringContentLength=”13107200” />
N Do not confuse these two lines with the similar lines that contain the following string: binding
name = "ProvisionServiceBinding".
3 Replace the number values assigned to the maxReceivedMessageSize and maxStringContentLength
aributes with a larger value.
The optimal size depends on how many more objects you expect your VMware vSphere cluster to
contain in the future. For example, you can increase these numbers by a factor of 10 for testing.
4 Save your changes and close the le.
5 Restart the vRealize Automation manager service.
Distributed Execution Manager Performance Analysis and Tuning
You can view the total number of in progress or pending workows at any time on the Distributed
Execution Status page, and you can use the Workow History page to determine how long it takes to run a
given workow.
If you have a large number of pending workows, or if workows are taking longer than expected to nish,
add more Distributed Execution Manager (DEM) Worker instances to pick up the workows. Each DEM
Worker instance can process 30 concurrent workows. Excess workows are queued for execution.
You can adjust workow schedules to minimize the number of workows that start simultaneously. For
example, rather than scheduling all hourly workows to run at the beginning of the hour, you can stagger
their run times so that they do not compete for DEM resources. For more information about workows, see
the vRealize Automation Extensibility documentation.
Some workows, particularly certain custom workows, can be CPU intensive. If the CPU load on the DEM
Worker machines is high, consider increasing the processing power of the DEM machine or adding more
DEM machines to your environment.
Chapter 4 vRealize Automation Scalability
VMware, Inc. 19