Key Figures
JS7 is designed for performance. There are no hard-wired performance limits. Therefore The key figures indicate the numbers that JS7 has been tested for, this doesn't with. They do not indicate a limit:.
1 000 000| 500 000 | The overall number of orders |
managed | for execution of workflows |
| Total of Workflows | 200 000 | The overall number of workflows |
|---|
each including a minimum of 5 jobs500 000| 1 000 000 | The number of jobs available |
across any Total of Parallel Tasks per Agent | | Total of Parallel Tasks per Agent | 15 |
|---|
5 | 000 | The number of parallel processes running with a single Agent |
Total of Parallel Tasks across Agents | 20
| Total of Parallel Tasks across Agents | 50 000 | The number of parallel processes running across any Agents |
|---|
Task Start Latency | 5 ms
| Task Start Latency | 5 ms | The delay in milliseconds between the request to start a task and the operating system process being started |
|---|
Performance Factors
- Controller and Agents make use of any all available cores to parallelize threads. A larger number of cores allows better parallelism.
- Memory usage of Controller and Agents has to be adjusted to the expected parallelism. As a rule of thumb e.g. running 5000 parallel tasks suggests a minimum of 8 GB main memory for each Controller and Agent.
- Disk speed is relevant for the Controller and Agent journal that stores any state transition events of ordersjournals that hold events for JS7 - Order State Transitions.