UiPath Orchestrator Guide

Hardware Requirements

Production Environment

These hardware requirements apply to large scale deployments with 100 Robots per Node.

Web Application Server

Minimum
Recommended

CPU

8 X 2.4Ghz cores

16 X 2.4Ghz cores

RAM

8GB

16GB

Disk *

100 GB HDD

100 GB SSD

Logs **

5 GB/per day

10 GB/per day

SQL Server

Minimum
Recommended

CPU

8 X 2.4Ghz cores

16 X 2.4Ghz cores

RAM

16GB

32GB

HDD *

200-300GB

600-800GB

ElasticSearch Server

Important!

The following requirements are guidelines. Please see the official ElasticSearch requirements.

Minimum
Recommended

CPU

4 X 2.4Ghz cores

8 X 2.4Ghz cores

RAM

16GB

32GB

HDD **

200-300GB

500-600GB

OS

  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016
  • RedHat Linux
  • Ubuntu 16
  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016
  • RedHat Linux
  • Ubuntu 16

Important!

Network Load Balancer - A Network Load Balancer (hardware or even software NLB, like NGINX, Zen Load Balancer, HAProxy etc.) is required when Orchestrator is installed on multiple servers in a High Availability configuration.

Disk space requirements highly depend on:

  • whether work queues are used or not; if work queues are used, it depends on average number of transactions added daily/weekly and size (number of fields, size of each field) of each transaction
  • the retention period for successfully processed queue items (the customer should implement their own retention policy)
  • whether messages logged by the robots are stored or not in the database; if they are stored, a filter can be applied to only store in the DB specific levels of messages (for example, store in the DB the messages with log level “Error” and “Critical”, and store in ElasticSearch messages with log level “Info”, “Warn” and “Trace”)
  • the frequency of logging messages - the robot developer uses the “Log Message” activity at will, whenever they consider a message is worth to be logged;
  • the retention period for old logged messages (the customer should implement their own retention policy)
  • logging level value set up in the robot; for example, if logging level in the robot is set to “Info”, only messages with levels “Info”, “Warn”, “Error” and “Critical” are sent to Orchestrator; messages with levels “Debug”, “Trace” and “Verbose” are ignored, they will not reach Orchestrator.

Disk space requirements depend on:

  • the retention period (the customer should implement their own retention policy)
  • the frequency of logging messages - the robot developer uses the “Log Message” activity at will, whenever they consider a message is worth to be logged;
  • logging level value set up in the robot; for example, if logging level in the robot is set to “Info”, only messages with levels “Info”, “Warn”, “Error” and “Critical” are sent to Orchestrator; messages with levels “Debug”, “Trace” and “Verbose” are ignored, they will not reach Orchestrator.

Large Scale Production Environment

The following environment is recommended to run 10K Robots:

  • An F5 load balancer.
  • Orchestrator - at least 6 instances that run on machines with 8 CPU Cores and 16 GB RAM.
  • Robots - machines with 4 CPU Cores and 16 GB RAM
  • SQL Server - machines with 16 CPU Cores and 32 GB RAM

The SQL machine has to be configured with 4 sockets/16 cores (default 8 sockets/16 cores).
A standard web.config file with the following adjustments:

  • The database connection pool on each Orchestrator instance set to 200 (default 100).
  • Configure the logging method to only use ElasticSearch and disable the Database target.

Note that logging to the database can significantly slow down the process, especially if your workflow contains errors. In case you do want log to database, then set the NLog module buffer size to 10 (default 100).

You can also check out hardware requirements for Studio and Robot.


Hardware Requirements