-
Enhancement
-
Resolution: Fixed
-
P4
-
18
-
b25
This can impact pause time significantly in g1 as it needs to clear the young gen card table in the pause.
If you increase the card table entry size, there may be significant savings on that time when the amount of regions the card table has to be cleared is large, as the attached spreadsheet shows for specjbb2015.
See what the impact on other applications and garbage collectors is when increasing the card table size, effectively making it startup time configurable.
- csr for
-
JDK-8275142 Configurable card table card size
-
- Closed
-
- relates to
-
JDK-8334010 VM crashes with ObjectAlignmentInBytes > GCCardSizeInBytes
-
- Resolved
-
-
JDK-8277854 The upper bound of GCCardSizeInBytes should be limited to 512 for 32-bit platforms
-
- Closed
-
-
JDK-8277373 Make maximum card table size dependent on ObjectAlignmentInBytes
-
- Open
-
-
JDK-8277450 Record number of references into collection set during gc
-
- Resolved
-
-
JDK-8328364 Remove redundant fields in 'BOTConstants'
-
- Resolved
-
-
JDK-8272774 Allow heap region sizes larger than 32M with larger card table entry sizes
-
- Closed
-
-
JDK-8309627 Incorrect sorting of DirtyCardQueue buffers
-
- Resolved
-
-
JDK-8227174 Lazily set card table of allocated regions to correct values in G1
-
- Open
-
-
JDK-8278901 Parallel: Investigate impact of card size on card scanning work distribution
-
- Open
-
-
JDK-8275056 Virtualize G1CardSet containers over heap region
-
- Resolved
-
-
JDK-8277372 Add getters for BOT and card table members
-
- Resolved
-