JDK-8199513 : Release Note: Garbage Collectors Adaptively Scale the Number of Threads by Default
- Type: Sub-task
- Component: hotspot
- Sub-Component: gc
- Affected Version: 11
- Priority: P4
- Status: Closed
- Resolution: Delivered
- Submitted: 2018-03-13
- Updated: 2019-04-09
- Resolved: 2018-10-18
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 |
|---|
11Resolved  |
Related Reports
|
Relates :
|
Description
The number of threads garbage collectors use in the garbage collection stop-the-world pauses determine the number of threads to use based on the maximum size of the Java heap. The flag -XX:UseDynamicNumberOfGCThreads is now true (enabled) by default. This improves startup time and reduces resource usage particularly for Java applications run with a small Java heap. If you experience performance reductions particularly on applications that use a small amount of Java heap, you can disable this new behavior by specifying -XX:- UseDynamicNumberOfGCThreads on the command line.