-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b31
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083358 | emb-9 | Mikael Gerdin | P4 | Resolved | Fixed | b31 |
JDK-8063322 | 8u45 | Mikael Gerdin | P4 | Resolved | Fixed | b01 |
JDK-8059107 | 8u40 | Mikael Gerdin | P4 | Resolved | Fixed | b08 |
JDK-8071058 | emb-8u47 | Mikael Gerdin | P4 | Resolved | Fixed | team |
During the G1 Class Unloading project we found that we spend significantly more time in the "Code Root Migration" time than the time spent scanning the code remembered sets. When G1 starts to unload more objects out of old regions the heuristics find more opportunities to include old regions in the mixed GCs. This has the effect that G1 with Class Unloading sometimes experience longer mixed GC times compared to a build without G1 Class Unloading.
We need to fix this performance problem.
- backported by
-
JDK-8059107 G1 Code Root Migration performs poorly
-
- Resolved
-
-
JDK-8063322 G1 Code Root Migration performs poorly
-
- Resolved
-
-
JDK-8071058 G1 Code Root Migration performs poorly
-
- Resolved
-
-
JDK-8083358 G1 Code Root Migration performs poorly
-
- Resolved
-
- duplicates
-
JDK-8030157 Serial G1 code root migration phase causes long pauses
-
- Closed
-
- relates to
-
JDK-8051608 Improve performance of Code Root Migration
-
- Closed
-
-
JDK-8056084 Refactor Hashtable to allow implementations without rehashing support
-
- Closed
-
-
JDK-8048248 [Backed out] G1 Class Unloading after completing a concurrent mark cycle
-
- Resolved
-
-
JDK-8049421 G1 Class Unloading after completing a concurrent mark cycle
-
- Resolved
-