Hardware Sizing

Sizing is the process of determining the hardware requirements for different slabs of workload. This document provides guidelines for the recommended hardware requirements to install and run Engage in client production environment. Use these guidelines for the detailed information on Server and Client specifications.

General Guidelines

The guidelines mentioned here are based on the validations carried out in testing environment under specific load conditions.

• The server usage in client environment will vary depending on the workload and amount of data in the system.
• It is recommended to periodically analyze the server resource utilizations and consider corrective measures.
• Periodic archival of the data is advised. If data storage in live system is mandatory, the configurations of the servers are to be reviewed based on the resource utilization levels seen at implementation site.
• The recommended server configurations will support number of users/bots as per slabs, number of automation requests processed, user types, automation complexities and functionalities implemented. As additional users/bots/workflows are added, requests processing count increased or new functionality implemented, additional resources may need to be added to the servers.

 

Scenarios

This section explains the Engage capacity plan scenarios for various usage scenarios. Refer the appropriate scenario depending on your implementation plan. 

Engage setup suggestions are based on load tests performed on various slabs of concurrent logged in users.

The physical to virtual cores ratio is considered to 1:2. That is, 1 physical core = 2 logical/virtual cores = 2 vCPUs

Reports:  The reporting function utilizations will depend on the data queried and frequency. The system has been tested for Engage reports from a total Transaction store size of 190 GB. If report requirements are of higher size and frequency, the capacity of the servers should be increased appropriately as per the utilization level observed at the implementation site.

The hardware recommendations below are based on the tests carried out in internal systems engineering Lab.

 

Engage Capacity Plan Scenarios

For Engage, the capacity plan is provided as per below slabs:

 

Non-HA Deployment

• Deployment for up to 200 logged in users
  
  Deployment to cater up to 200 logged in users. Engage components are in single replica.
  

  NOTE:

  Non-HA environment depicts the scalability of the application. High Availability setup is recommended in Production environment.

 

 

HA Deployment

• Deployment for up to 500 logged in users
  
  Deployment to cater up to 500 logged in users. Engage components are in cluster setup.
  

  NOTE:

  Logged in users are the users who have logged into the Engage application at the given time.

  
  

Hardware Recommendations

Engage Deployment for Non-HA (Up to 200 Users)

 

 

 

 

Engage Deployment for HA (Up to 500 Users)

 

 

Engage component and version details:

 

 

 

Common Setup details:

 

Suggestions

Refer Hardware Sizing recommendations for the different supported scenarios for automation deployment. In addition, following are a few generic recommendations:

• Adjust/ increase heap size of OpenSearch based on the total number of robots and concurrent requests being processed.
• Ensure appropriate Load Balancer settings in HA deployment to ensure that load is distributed evenly amongst the different nodes of the configured cluster.

 

NOTE:

Staging environment is not included in any of the scenarios.

Automation Studio Client/ Development Components

Below requirements are applicable for Automation Studio and Robot Farm. 

 

Technical Component	Hardware Requirement	Remarks
Automation Instance	Minimum: 2 Core (4vCPU), 8+ GB RAM NOTE: Disk space: 1 GB for product binaries. Remaining disk space to be calculated based on number of Robots and expected log size etc. consideration.	Minimum head room required for the client tools is 15% of CPU and 120 MB RAM
Automation Studio

 

 

 

NOTE:

The configuration of Automation Instance in machine is dependent on the applications being used in the system. The overall planning is to be done considering the resource utilization by all the applications running parallelly in the system.