When the PingFederate installer for Windows runs the memoryoptions utility tool or when changes are made from a manual edit, expect the following behaviors to the installation medium.
The PingFederate installer for Windows runs the memoryoptions utility in an attempt to optimize the Java virtual machine (JVM) heap. Regardless of available memory, PingFederate uses the Garbage-First (G1) garbage collector (GC). The script assumes that PingFederate will be the only service on the server and consume a majority of the memory.
The G1GC is designed to achieve high throughput while meeting its pause times goal for garbage collection, and the collector self-tunes by adjusting the size and nature of the various heap regions to meet the pause time goal. As needed, administrators can rerun the utility or manually edit these options at a later time.
When the PingFederate installer is executed for Windows or a subsequent rerun of the memoryoptions utility, it creates a backup copy of the current jvm-memory.options and records the G1GC options in the jvm-memory.options file. Changes made as a result of the execution of the utility or a manual edit are activated after a restart of PingFederate.
You should not use the
memoryoptions script when you deploy PingFederate inside of a container. Instead, you should edit
jvm-memory.options file directly. In containers, you should use the
options to control the size of the heap.
See the following table for information regarding expected behaviors.
|Installation medium||Expected behavior|
|PingFederate installer for Windows||
|PingFederate product distribution ZIP file||The default jvm-memory.options file becomes part of
the new installation as program and default configuration files are extracted
from the PingFederate product distribution .zip file.