...

• Vertical Scalability
  • There are no built-in limits as to the overall number of jobs and number of parallel job executions per Controller and Agent.
  • A single Controller is tested for some 50 000 parallel tasks, a single Agent is tested for approx. 15 000 parallel tasks.
  • Adding more power to a single machine (CPU, Memory, SSD Disks) will improve performance as the components products will make use of all available cores.
• Horizontal Scalability
  • Splitting the job load across a number of Agents will push the number of parallel tasks.

...

• The following indicators should be considered:
  • The overall number of workflows and jobs that will be available.
  • The number of jobs that will be executed in parallel.
• Number of Jobs
  • Small environments are assumed to use < 1 000 jobs, medium sized environments use < 20 000 jobs, larger environments use larger numbers.
• Parallelism of Jobs
  • Small environments run < 100 parallel jobs, medium sized environments run < 1 000 parallel jobs, larger environments run larger numbers of jobs.

Basic Recommendation

The recommendation indicates dedicated resources available to JS7 products. Resource usage by additional software running on a machine come on top.

...

• 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.
• 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.

...

• Journal files
  • Journal files are used by Controller instances and Agent instances to store information about state transitions and log output. Typically such information is immediately forwarded from an Agent to the Controller and from the Controller to JOC Cockpit. However, in case of high load or outage of a component product such as a Controller, then the Agent will continue to execute jobs and store such information in its journal. Journal files therefore can grow, technically to the max. size imposed by the OS. Journal files will shrink after JS7 components products are recoupled. For most situations with <100 000 job executions per day and an outage period < 24h it is sufficient to assume 5 GB diskspace for journal files. 
• Log files
  • Log files are by default configured for log rotation to limit diskspace consumption and to restrict the number of files in use, see the JS7 - Log Rotation article for more information.
    
    • All log files are controlled by Log4j2 and allow individual configuration.
    • By default diskspace consumption is limited to 5 GB and log files are retained for 30 days. This applies to each JOC Cockpit, Controller and Agent.
  • Recommendations
    • It is suggested that not less than 1 GB disk space is assigned for logs. Use of more than 5 GB disk space should be required only if the retention period for log files is prolonged.
    • When JS7 components products cannot write to a log file then they will be blocked from further operation. To prevent such a situation add a disk space monitoring task to your system monitor.

...

Further Resources

• JS7 - Performance
• JS7 - FAQ - Which Java Options are recommended
• JS7 - How To - Apply Java Options