Unattended automation capacity planning - Plan your capacity and performance for Control Room On-Premises , understand the requirements, limits, and defaults that determine the number of simultaneous automations, user sessions, and processing rates for unattended automations.

Plan your capacity and performance for Control Room On-Premises, understand the requirements, limits, and defaults that determine the number of simultaneous automations, user sessions, and processing rates for unattended automations.

Overview

Review the information on the maximum number of concurrent automation deployments and executions for On-Premises deployment.

The entity count in the following list provides information about the maximum number of entities that the Control Room can support irrespective of the machine resources. Deploying additional machine resources does not increase the entity count.

Control Room supports either of the following, for maximum number of concurrent automation deployments and executions:

1000 devices for 1000 concurrent automation deployments and executions on Bot Runner sessions (typically in a production Control Room).
700 devices for 700 concurrent automation deployments and executions on Bot Creator sessions (typically in a development Control Room).


Entity Type	Count
Users	10,000³
Roles	5000³
Schedules	1500
Audit entries	10,000,000³
Lockers	100
Credentials	5000
Repository files¹ (Including all file types in the Control Room Public workspace)¹	100,000³
Repository folders²	9000³
Queues	100
Device pools	100
Work Items	30 million

Repository files include dependent files that you check in to the Public workspace (visible on the UI) such as Task Bots, .atmx, .dll, .txt, .csv, and so on, and the related files from the database (not visible on the UI). For example, .png files generated after an automation is recorded are stored in the database and are included in the repository files.
Applies to the public workspace.
Applicable from Automation 360 v.21 and later.

Concurrent automation deployments and executions

Control Room supports up to 1000 concurrent automation deployments and executions across the Control Room cluster. These 1000 automations can be a combination of the same or different automations.

Note: If you use different automations, because of the load, the compiler slows down the execution for the first-time deployment. For subsequent deployments, automation execution process might accelerate.


Control Room edition and configuration	Number of Run as users
One instance of On-Premises	Maximum 1000
Three instances of On-Premises with High Availability (HA) configuration	Maximum 1000

The automation deployment depends on the network quality and the size of data that needs to be transferred from Control Room to Bot Agent.

Therefore, in the above scenario when the network connectivity speed is increased for the three Control Room instances, the network throughput improves, so the completion time will become shorter but the maximum accepted concurrent automation deployments will remain the same.

Automation concurrent schedules

Scheduling considerations when running automations repeatedly.

When configuring automations to run repeatedly on a schedule it is important to make sure that the time between runs does not drop below the total time for deployment and execution of the automation. Otherwise, sequential executions of the automation might overlap leading to unexpected behavior.

For example if it takes two (2) minutes to run a automation, do not schedule the automation to run every one (1) minute. The previous run cannot complete before the next run begins.

With the reference specification, it is possible to successfully configure concurrent schedules.


Activity	Schedule data
Concurrent schedules	100
Run as user per schedule	10
Total concurrent automations	1000