...
- Impact
- Starting from your architecture decision the distribution of jobs across Master and Agent instances should be considered.
- Jobs that are executed on Agents do not result in CPU and memory requirements on the Master.
- Jobs that are executed agentless by SSH require a process that is executed on the Master and a process on the SSH server for execution of the job script.
- For each job executed in parallel a JobScheduler instance the following resources are required:
- A Java Virtual Machine is started that requires at least 32 MB memory. When using API jobs or JITL jobs then this value could be increased to 64 MB.
- The scripts and programs that you execute will cause individual requirements converning CPU and memory.
- When running jobs for database processing then the load will be in the database and not on the JobScheduler instance. CPU and memory requirements are usually stable for such jobs independent from the size or duration of transactions that are performed by such jobs.
- Starting from your architecture decision the distribution of jobs across Master and Agent instances should be considered.
- Recommendations
- Calculate at least 32 MB memory for each job, e.g. 7 GB memory for approx. 200 parallel job executions.
- Consider to share the load by use of Agents that are executed on different servers.
CPU
- ImpactStarting Point
- JobScheduler has a low footprint when it comes to CPU usage. Practically no CPU usage applies to idle jobs and monitored directories.
- Recommendations
- Do not use a single CPU system. Situations could occur when individual job scripts might misbehave and consume more CPU than expected. A second CPU allows to have process resources in a situation when the first CPU is blocked.
Memory
- ImpactStarting Point
- The JobScheduler Master requires about 200 MB memory.
- The JobScheduler Universal Agent has a footprint of about 50 MB memory.
- Recommendations
- Calculate at least 32 MB memory for each job, e.g. 7 GB memory for approx. 200 parallel job executions.
...