Action Center
2021.10
false
- Release Notes
- Before you begin
- Getting Started
- Installation and upgrade
- Actions
- Processes
- Troubleshooting
Multi-Node Deployments
Action Center User Guide for Standalone
Last updated Mar 24, 2023
Multi-Node Deployments
We ran performance tests to mimic a large load on Action Center and Orchestrator, with the following sample data:
- 10,000 concurrent Action Center users
-
240,000 actions
- 60% document validation actions
- 40% form actions
-
Payload per one form action:
- Form layout—5KB
- Form data—5KB
- 10 storage files x 100KB
-
Payload per one document validation action:
- One PDF file x 150KB
Based on our performance tests, we recommend the maximum numbers below:
- 150,000 attended robots connected to Orchestrator and running jobs
- 10,000 Action Center users processing actions
- 3,000 unattended robots running jobs (creating actions and resuming after the actions completion)
To ensure seamless performance for the above scenario, we recommend setting the following environment:
Instance |
No. of Deployment Nodes |
Azure VM |
vCPU Cores |
Frequency (GHz) |
RAM (GB) |
---|---|---|---|---|---|
Action Center |
3 |
B2s |
2 |
2.0 |
4 |
Orchestrator |
10 |
F16 |
16 |
2.0 |
32 |
SQL Server |
1 |
F32 |
32 |
2.0 |
64 |
Allocate a drive for each of the following content:
Stored Content |
Drive Capacity |
---|---|
Database |
1TB |
Temporary database |
1TB |
Transactional logs |
1TB |