In order to ensure cost efficiency, all CirrusGrid-managed Java servers are automatically configured to utilize memory in the most beneficial way by adjusting the main Java memory parameters based on the amount of resources, allocated to a container.
Tip: Non CirrusGrid-managed Java-based containers can be optimized in a similar way using the Java Memory Agent add-on.
Herewith, for a high performance or any other custom configurations, the default options can be manually changed.
1. In order to provide all the preferred Java options at once, the variables.conf file can be utilized.
Depending on a particular application server you are working with, the exact location may vary:
If needed, you can redefine the main memory options via container variables.
2. Don’t forget to Restart nodes to apply changes.
That’s it! Now, your application is running with your custom Java options.
The most essential memory parameters (-Xms, -Xmn, -Xmx, -Xminf, -Xmaxf, -XX:MaxPermSize, *-XX:+Use.GC) can be redefined using the dedicated environment variables.
As an example, you can Add the -Xmx option (i.e. maximum size for the Java heap memory):
When operating with the Spring Boot and Java Engine templates, you can provide two additional variables:
Don’t forget to restart your application server(s) in order to apply changes.
Powered by BetterDocs
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.