To ensure optimal distribution of physical memory, a user should be aware of the fact that CloverDX Server is using two separate JVMs: Core (runs Server Web Console, user management, scheduler, data services, etc.) and Worker (executes transformation graphs and jobflows). For more information see the CloverDX Server Architecture documentation chapter.
Default JVM memory settings are rather conservative for running an application container with CloverDX Server. The recommended values of Server Core heap size and Worker heap size for different RAM sizes can be found at the following link:
The above may need to be adjusted in accordance with the overall software architecture, operating system, and the nature of the tasks being executed.
- The Core memory setups are managed on the application server level and you can find the details in the installation-related section in the documentation (on the page, select the application server your instance is using for more details):
As it is stated in the documentation, you can set the initial and maximum memory heap size by adjusting the Xms and Xmx JVM parameters. Advanced users can also set other JVM parameters in the same place (related to Metaspace, Direct memory, or Garbage collecting).
- The Worker memory can be then handled in the Server GUI. Go to the Configuration -> Setup -> Worker -> Maximum heap size (MB) field