...

Heap size depends on memory consumption of each JS7 component product which is related to:

• the number of parallel users working with JOC Cockpit,
• the number of workflows deployed to Controllers and Agents,
• the number of parallel tasks,
• the maximum outage duration that is assumed for the connection between Agent and Controller as well as for the connection between Controller and JOC Cockpit..

...

• The Agent can be operated initially with 100 MB heap size i.e. -Xms100m.
• By default no maximum heap size is assigned - that is, the Agent will be assigned the heap size calculated by Java when starting the Java Virtual Machine.
• Heap size can grow up to the specified maximum -Xmx1g based on performance indicators such as:
  • the number of workflows deployed to the Agent,
  • the number of parallel tasks executed with the Agent,
  • the max. failure time for which the Agent is not connected to a Controller.
• The above values should work for approx. 10 000 workflows with a max. failure time of 24 hours.

Threads

JS7 components products make use of multithreading which is dynamically assigned according to the available CPU cores.

...