UiPath Orchestrator Guide

Hardware Requirements

For Demo, Development and Test Environments

These hardware requirements apply to medium-scale deployments with 10 to 50 Robots (Option 1 from the UiPath Orchestrator Architecture Guide).

Version 1 – Three Servers

Web Application Server

Minimum
Recommended

CPU

2 X 1.8Ghz cores

4 X 2.4Ghz cores

RAM

4GB

8GB

HDD

50GB

100GB

SQL Server

Minimum
Recommended

CPU

2 X 1.8Ghz cores

4 X 2.4Ghz cores

RAM

6GB

12GB

HDD *

80GB

150GB

ElasticSearch Server

Minimum
Recommended

CPU

2 X 1.8Ghz cores

4 X 2.4Ghz cores

RAM

6GB

12GB

HDD **

100GB

250GB

OS

Windows Server 2008 R2 SP1, Windows Server 2012 R2, Windows Server 2016, RedHat Linux, Ubuntu 16

Windows Server 2008 R2 SP1, Windows Server 2012 R2, Windows Server 2016, RedHat Linux, Ubuntu 16

Version 2 - Two Servers

SQL Server

Minimum
Recommended

CPU

2 X 1.8Ghz cores

2 X 2.4Ghz cores

RAM

6GB

12GB

HDD *

80GB

150GB

Web Application Server and ElasticSearch

Minimum
Recommended

CPU

2 X 2.4Ghz cores

4 X 2.4Ghz cores

RAM

8GB

16GB

HDD **

150GB

250GB

OS

Windows Server 2008 R2 SP1 OR Windows Server 2012 R2 OR Windows Server 2016

Windows Server 2008 R2 SP1 OR Windows Server 2012 R2 OR Windows Server 2016

* Disc 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.

** Disc 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.

Production Environment

These hardware requirements apply to large scale deployments with 100 to 200 Robots (Option 2 from the UiPath Orchestrator Architecture Guide).

Web Application Server

Minimum
Recommended

CPU

4 X 2.4Ghz cores

8 X 2.4Ghz cores

RAM

8GB

16GB

HDD

80GB

150GB

SQL Server

Minimum
Recommended

CPU

4 X 2.4Ghz cores

8 X 2.4Ghz cores

RAM

12GB

32GB

HDD *

200-300GB

600-800GB

ElasticSearch Server

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 OR Windows Server 2012 R2 OR Windows Server 2016, RedHat Linux, Ubuntu 16

Windows Server 2008 R2 OR Windows Server 2012 R2 OR 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) is required when Orchestrator is installed on multiple servers in a High Availability configuration.

* Disc 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.

** Disc 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.

You can also check out hardware requirements for Studio.


Hardware Requirements