You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

Use of Java Options depends on the Java release in use.

  • Typically earlier Java releases include features that are not active by default.
  • Such features can be active by default in later releases.

Heap Size

Heap size depends on memory consumption of each JS7 component that 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 that is resumed for the connection between Agents and Controller as well as the connection between Controller and JOC Cockpit.

For more details see JS7 - Sizing.

Find a few recommendations to start with


Specify minimum and maximum heap size for JOC Cockpit
JAVA_OPTIONS="-Xms500m -Xmx1g"
Specify minimum and maximum heap size for Controllers
JAVA_OPTIONS="-Xms500m -Xmx1g"
Specify minimum and maximum heap size for Agents
JAVA_OPTIONS="-Xms100m -Xmx1g"

Threads

xss

Garbage Collector

  • It is recommended to activate the G1 Garbage Collector
  • This applies to Java releases 1.8 to 11.
  • For Java 17 G1 is the default Garbage Collector.


Activate G1 Garbage Collector
JAVA_OPTIONS="-XX:+UseG1GC"

String Deduplication

  • String deduplication reduces memory consumption.


Activate String Deduplication
JAVA_OPTIONS="-XX:+UseStringDeduplication"




  • No labels