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

 

Hardware Configurations

This section explains the Engage capacity plan scenarios for various usage scenarios. Seethe appropriate scenario depending on your implementation plan. An update to this document will provide guidance on different slabs per scenario and recommended hardware sizing.

 

Below suggestions for RPA setup are based on the automation processing load of up to 8 requests per hour per bot based on the automation process execution time.

 

Note: Below guidelines do not indicate the minimum hardware footprint of the platform for meeting a given usage scenario. The H/W guidelines are based on hardware provisioned for actual performance tests; these will be refined further to a more optimum recommended H/W based on follow-on tests.

 

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

 

Reports: The reporting function utilization depends on the data queried and frequency. The system has been tested for RPA reports from a total Open Distro store size of 224 GB and Engage reports from a total Open Distro store size of 150GB. 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 mentioned below are based on the tests carried out. The numbers will be revised with test results from the increased load.

For requirements not mentioned in the document, please get in touch with the product team.

 

Scenarios

This section explains the Engage capacity plan scenarios for various usage scenarios. Seethe 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 Elastic store size of 224 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.

 

AssistEdge Engage Capacity Plan Scenarios

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

 

Non-HA Deployment

• Deployment for up to 50 logged in users
  
  Deployment to cater up to 50 logged in users. Web and App components are in single server.
• Deployment for up to 300 logged in users
  
  Deployment to cater up to 300 logged in users. Web and App components are in single server.

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. Web and App components are in cluster setup.
• Deployment for up to 1000 logged in users
  
  Deployment to cater up to 1000 logged in users. Web and App components are in cluster setup.
• Deployment for up to 2000 logged in users
  
  Deployment to cater up to 2000 logged in users. Web and App components are in cluster setup.

NOTE:

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

AssistEdge Engage with Low Code Orchestrator Capacity Plan Scenarios

For AssistEdge Engage with low code orchestrator (web engage) the capacity plan is provided as per below slabs:

 

Non-HA Deployment

• Deployment for up to 50 logged in users
  
  Deployment to cater up to 50 logged in users. Web and App components are in single server.
• Deployment for up to 300 logged in users
  
  Deployment to cater up to 300 logged in users. Web and App components are in single server.

  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. Web and App components are in cluster setup.
• Deployment for up to 1000 logged in users
  
  Deployment to cater up to 1000 logged in users. Web and App components are in cluster setup.
• Deployment for up to 2000 logged in users
  
  Deployment to cater up to 2000 logged in users. Web and App 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: Non-HA and HA Deployment

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

NOTE:

Storage in app server should be determined based on number of automation requests processed in a day and associated complexity of the automation process. se-actvttrack-<date> index in elastic search can be used to monitor and determine the data storage needs. Non-HA environment depicts the scalability of the application. High Availability setup is recommended in Production environment.

 

Engage with Low Code Orchestrator: Non-HA and HA Deployment

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

NOTE:

Storage in app server should be determined based on number of automation requests processed in a day and associated complexity of the automation process. se-actvttrack-<date> index in elastic search can be used to monitor and determine the data storage needs. Non-HA environment depicts the scalability of the application. High Availability setup is recommended in Production environment. DB size needs to be monitored as it depends on the usage of the Low Code Orchestrator. Accordingly, the DB storage and archival policy can be determined.

 

Following are the recommendations for setting up of heap size:

 

 

 

 

 

 

 

Suggestions

Following are the guidelines on server types in Azure and AWS:

 

Azure: Corresponding configuration in General Purpose D series can be looked at for production implementations.

 

AWS: Corresponding configuration in General Purpose M series can be looked at for production implementations.

 

See AssistEdge Hardware Sizing recommendations for the different supported in Scenarios for automation deployment. In addition, following are a few generic recommendations:

• Adjust/ increase heap size of ElasticSearch based on the total number of robots and concurrent requests being processed.
• Sizing for machines running robots should factor resource utilization by 3^rd party client applications and number of bots planned in the machine.
• 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.

Engage-Automation Studio Client/ Development Components

Below requirements are applicable for Engage Client, Automation Studio and Robot Farm.

 

 

 

 

 

 

 

 

 

 

 

 

NOTE:

The configuration of Engage Client 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.