What is the maximum load a single node Orchestrator can bear? And what are the things responsible in increasing the load on single node Orchestrator to fail?
The maximum load that a single-node Orchestrator can bear depends on various factors, including the hardware specifications of the server, the complexity and resource requirements of your automation processes, the number of robots and concurrent jobs, and the configuration of your Orchestrator. It is important to understand the factors that can increase the load on a single-node Orchestrator and potentially lead to failure:
- Hardware Resources:
- CPU: The CPU's processing power is crucial for handling job scheduling, process execution, and managing the Orchestrator's operations.
- Memory (RAM): Sufficient memory is needed to store process data, logs, and manage concurrent processes and jobs.
- Storage: Adequate storage space is required for log files, database storage, and process packages.
- Number of Robots:
- The number of robots connected to the Orchestrator can significantly impact its load. More Robots mean more processes to manage, which requires more system resources.
- Concurrent Jobs:
- Orchestrator can handle multiple concurrent jobs. The more concurrent jobs you have, the more CPU and memory resources are required.
- Complexity of Processes:
- Complex automation processes with high computational requirements, long execution times, or numerous activities can strain the Orchestrator.
- High-Frequency Triggers:
- Frequent triggers and schedules can increase the load on the Orchestrator. Processes triggered at short intervals can lead to job queue congestion.
- Logging and Database Load:
- Extensive logging and database activity can consume resources. It's important to manage log levels and consider database performance for Orchestrator's data storage.
- Large Orchestrator Database:
- A growing Orchestrator database can increase resource usage. Regular maintenance, such as archiving old data, can help manage database size.
- External Integrations:
- Integrations with external systems, services, and applications can add to the load on Orchestrator, especially if they involve frequent data transfers.
- Security and Authentication:
- Extensive security measures, such as user authentication and access control, can require additional CPU and memory resources.
- Scheduled Maintenance and Updates:
- Regular maintenance and updates of the Orchestrator can temporarily increase resource usage during the update process.
- Network Latency and Bandwidth:
- Orchestrator may be impacted by network latency and limited bandwidth, especially when orchestrating processes that interact with remote systems or cloud services.
To determine the maximum load a single-node Orchestrator can bear, conduct performance testing and monitoring. Load testing helps to identify the limits of the specific setup and hardware. If the Orchestrator experiences performance issues or failures due to high loads, consider optimizing the hardware, processes, and Orchestrator configuration. For extremely high loads or mission-critical applications, also explore scaling the Orchestrator infrastructure by adding additional nodes or using a load-balanced configuration.
Refer the official document to understand the hardware requirements to compete the load with the increased no. of Robots or defined Robots.