-
Suggestion
-
Resolution: Unresolved
-
None
-
87
-
49
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Problem Definition
Currently JIRA is not explicitly selecting a GC method to use. Most JIRA Server instances are using the oldparallel method or Concurrent (CMS) methods to handle the JAVA garbage collection.
Suggested Solution
By default, JIRA should come with the -XX:+UseG1GC JVM startup parameter.
Why this is important
- Improved performance on environments with large heaps
- consistent GC method across initial deployments
- The Tuning garbage collection guide explicitly recommends using G1GC, but neglects to inform users on how to enable it
Workaround
JIRA Admins are able to manually enable the G1GC method by following the steps in Setting properties and options on startup and adding the parameter of
-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent
to the JVM_SUPPORT_RECOMMENDED_ARGS= section of the <JiraInstallDir>/bin/setenv.[sh|bat] file.
- is related to
-
JRASERVER-67885 Ship Jira with increased CodeCache size
- Closed
-
JRASERVER-70459 As a Jira admin, I want to have an easier way to set the flag -XX:+UseG1GC when using Java 11+
- Closed
- relates to
-
JRACLOUD-64331 Ship JIRA with G1GC enabled by default
- Closed
-
HL-1349 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...