JDK-8139652 : Mutator refinement processing should take the oldest dirty card buffer
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-10-15
- Updated: 2020-04-07
- Resolved: 2020-03-19
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 15 |
|---|
15 b16Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Currently, when a mutator helps refining a dirty card buffer, it refines the current buffer it just filled. In many situations this is not a good idea, because often the mutator will keep accessing the same memory areas again, immediately generating new card entries. Change the algorithm to use the last (oldest) buffer. There is a preliminary patch attached, needs perf testing.
Comments
|