...
- Number of jobs, job chains and orders
- This is about the number of job-related objects that are available in the system, independently from the fact that they are running or not.
- JobScheduler has to track events for jobs, e.g. when to start and to stop jobs. Therefore a high number of job related objects creates some performance impact. Common scenarios used in enterprise level environments include up to 20000 jobs and 10000 job chains in a single JobScheduler instance.
- Number of job nodes
- This is about the number of jobs that are used in job nodes for job chains. Jobs can be re-used for any number of job chains.
- You could operate e.g. 1000 job chains with each using 5 job nodes with individual jobs which results in a total of 5000 individual jobs.
- You could operate e.g. 100 individual jobs that are used in 1000 job chains each using an individual sequence of 5 out of 100 jobs.
- The length of a job chain, i.e. the number of job nodes, is important:
- In the most common scenarios job chains with up to 30 job nodes are used.
- You can operate a single job chain with a medium number of e.g. 4000 job nodes. In fact this will have a slight effect on performance as JobScheduler has to check predecessor and successor nodes for each job node.
Jira server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1566
- This is about the number of jobs that are used in job nodes for job chains. Jobs can be re-used for any number of job chains.
Resource Consumption
Consider what resources are consumed when running jobs:
...