This is a
video response to the HotSpot JVM garbage collection options cheat sheet recently posted by Alexey Ragozin. (Alexey lists so many
-XX options that I cannot help wondering if Sun had reserved any top-secret
-XXX ones for internal use. 😉 )
In contrast, what Excelsior JET users have does not look that much like a sheet, more like a sticky note:
||Maximum heap size. Defaults to a special value of
||Maximum percentage of CPU time spent on garbage collection, in tenths of a percent. Default: |
||Maximum number of concurrent threads that the garbage collector may use. By default, it utilizes all available CPU cores.|
1 Multi-app executables also recognize the
For details, refer to the Knowledge Base article HOWTO: Fine tune application memory footprint.
In addition, Excelsior JET Runtime has three flavors: Classic, Desktop, and Server, with availability depending on edition. The choice of Runtime affects the efficiency of memory allocation and garbage collection in multithreaded applications running on multi-core/multi-CPU systems. The default is set at compile time, but can be overridden using the
Do you need more control, or a memory manager that “just works”? Welcome to comments.