[JDK-8136678] Implement adaptive sizing algorithm for IHOP Created: 2015-09-17  Updated: 2017-05-19  Resolved: 2015-11-25

Status: Resolved
Project: JDK
Component/s: hotspot
Affects Version/s: 9
Fix Version/s: 9

Type: Enhancement Priority: P2
Reporter: Thomas Schatzl Assignee: Thomas Schatzl
Resolution: Fixed Votes: 0
Labels: gc-g1, gc-performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks JDK-8136679 JFR event for adaptive IHOP Resolved
is blocked by JDK-8140597 Forcing an initial mark causes G1 to ... Resolved
is blocked by JDK-8136681 Factor out IHOP calculation from G1Co... Resolved
CSR
csr of JDK-8199262 Implement adaptive sizing algorithm f... Closed
Duplicate
duplicates JDK-7097565 G1: adaptive policy for transitioning... Closed
Relates
relates to JDK-8141402 GC locker initiated GC ends mixed gc ... Closed
relates to JDK-8142484 Let IHOP follow the current capacity,... Resolved
relates to JDK-8140777 Make Adaptive IHOP logging informatio... Resolved
relates to JDK-8140689 Skip last young-only gc if nothing to... Resolved
relates to JDK-8136677 Adaptive sizing for IHOP in G1 Resolved
Subcomponent: gc
Resolved In Build: b96

 Description   
Add support for adaptive IHOP, recalculating that value every GC based on current heap size, allocation reserves, promotion rate and other metrics.

Support should be gated behind a new switch called -XX:+G1UseAdaptiveIHOP. Basic tracing should be provided using -XX:+PrintAdaptiveSizePolicy.

 Comments   
Comment by Thomas Schatzl [ 2015-09-17 ]
The changes should encapsulate the logic in a single G1IHOPControl (or similar class) that can be unit tested, plus unit tests.
Comment by HG Updates [ 2015-11-25 ]
URL: http://hg.openjdk.java.net/jdk9/hs-rt/hotspot/rev/b389867c9d1d
User: tschatzl
Date: 2015-11-25 21:17:35 +0000
Comment by HG Updates [ 2015-12-10 ]
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/b389867c9d1d
User: lana
Date: 2015-12-10 00:26:59 +0000
Generated at Sat Aug 24 02:58:28 UTC 2019 using Jira 7.13.5#713005-sha1:8d78f1047b9cca7d35d4d13f706b37e27d869e07.