-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
b23
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8010353 | 8 | Tao Mao | P3 | Resolved | Fixed | b82 |
We don't need the distinction between MaxGCMinorPauseMillis and MaxGCPauseMillis. The MaxGCMinorPauseMillis flag was introduced as a backup measure in case one pause target for all types collections was not enough.
As it has turned out it seems one pause target is enough. Thus, we should deprecate MaxGCMinorPauseMillis and give a warning when set.
As it has turned out it seems one pause target is enough. Thus, we should deprecate MaxGCMinorPauseMillis and give a warning when set.
- backported by
-
JDK-8010353 Deprecate MaxGCMinorPauseMillis
- Resolved
- relates to
-
JDK-8324301 Obsolete MaxGCMinorPauseMillis
- Resolved