JDK-8273192 : G1: Improve thread sizing for evacuation failure
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 18
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2021-08-31
  • Updated: 2021-11-30
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8256265 - G1: Improve parallelism in regions that failed evacuation
Relates :  
JDK-8276094 - Region Pinning in G1
Relates :  
JDK-8254167 - G1: Record regions where evacuation failed to provide targeted iteration
Description
JDK-8254167 tracks which regions failed evacuation; but probably thread sizing could be improved if we know how much work in total needs to be done.

E.g. assuming we have better per-region thread distribution (JDK-8256265), the number of threads could be determined by actual work not just by number of regions.
Comments
What's the unit should we use to calculate the work cost? objects number? then, what's the threshold for one thread?
09-11-2021