DevTest - Garbage Collector Settings
Article ID: 112719
Updated On:
Products
CA Application Test
CA Continuous Application Insight (PathFinder)
Issue/Introduction
If increasing the memory does not solve an out or memory issue or a performance problem, changing to a high performance garbage collector may solve the problem.
Environment
All supported DevTest releases.
Resolution
These settings can apply to any DevTest component.
However, the most common components are Registry, VSE and Portal.
These changes will be made in the .vmoptions for the specific component.
Example:
For the Registry, make the changes in both the Registry.vmoptions and the RegistryService.vmoptions files.
Note: Making the change in both vmoptions files is recommended.
If the total memory for the DevTest component is 4 GB or less, add these properties:
-XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode
-XX:+CMSIncrementalPacing
-XX:MaxGCPauseMillis=500
If the total memory for the DevTest component is greater than 4 GB, add these properties:
XX:+UseG1GC
-XX:MaxGCPauseMillis=200
After making the change, the DevTest component must be restarted.
However, the most common components are Registry, VSE and Portal.
These changes will be made in the .vmoptions for the specific component.
Example:
For the Registry, make the changes in both the Registry.vmoptions and the RegistryService.vmoptions files.
Note: Making the change in both vmoptions files is recommended.
If the total memory for the DevTest component is 4 GB or less, add these properties:
-XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode
-XX:+CMSIncrementalPacing
-XX:MaxGCPauseMillis=500
If the total memory for the DevTest component is greater than 4 GB, add these properties:
XX:+UseG1GC
-XX:MaxGCPauseMillis=200
After making the change, the DevTest component must be restarted.
Feedback
Yes
No
Powered by
