Page History
...
| Job Inventory | Parallel Executions | JOC Cockpit | Controller | Agent | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Cores | Memory | Storage | Cores | Memory | Storage | Cores | Memory | Storage | |||
| Small | < 1 000 | < 100 | 2-4 | 512 MB | 6 GB | 2 | 250 256 MB | 5 GB | 2 | 100 MB | 5 GB |
| Medium | < 20 000 | < 1 000 | 2-4 | 1 GB | 10 GB | 2-4 | 1 GB | 10 GB | 2-4 | 1 GB | 10 GB |
| Large | >= 20 000 | >= 1 000 | 4-8 | 2 GB | 10 GB | 4-8 | 4 GB | 10 GB | 4-8 | 4 GB | 10 GB |
...
- Impact
- The number of parallel orders and jobs increases memory consumption of an active Controller instance and the relevant Agents.
- The JOC Cockpit can be operated from 128 512 MB heap size. This value should be increased if more users are working in parallel with JOC Cockpit or if a larger number of orders are available in the JS7 - Daily Plan.
- The Controller can be operated starting from 128 256 MB memory. Higher parallelism of orders and jobs will require higher values, e.g. for 100 000 orders approx. 4 GB will be required.
- The Agent has a footprint of about 100 MB memory. As with the Controller higher parallelism of orders and jobs will push this value. As a rule of thumb 2 GB main memory should be sufficient to execute 5 000 jobs in parallel on an Agent.
- Refer to the JS7 - FAQ - Which Java Options are recommended article for default values and details how to specify memory consumption.
- The number of parallel orders and jobs increases memory consumption of an active Controller instance and the relevant Agents.
- Recommendations
- Calculate 500 MB for JOC Cockpit for 5 to 10 parallel users. Calculate 2 GB each for a Controller and Agent if < 50 000 task executions per day and < 5000 parallel task executions are performed. You can reduce the values for Controller and Agent to 500 MB if < 10 000 task executions per day and < 1000 parallel task executions are performed.
...
Overview
Content Tools