-
Enhancement
-
Resolution: Fixed
-
P3
-
hs15
-
b08
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2182195 | 7 | John Cuthbertson | P3 | Closed | Fixed | b71 |
| JDK-2181938 | 6u18 | John Cuthbertson | P3 | Resolved | Fixed | b01 |
We recently tried G1 on a 32GB heap, with a 4GB / 8GB young gen. We noticed that termination times are relatively long (around 30-40ms). The reason for this is that GC worker with id 0 (it's always GC worker with id 0) is late coming into the GC code which results in all the other threads waiting for it during termination. This is clearly a performance bottleneck. We should resolve this.
- backported by
-
JDK-2181938 G1: first GC thread coming late into the GC
-
- Resolved
-
-
-
- Closed
-
- duplicates
-
JDK-6817995 G1: Error: guarantee(!r->is_young(),"It was evicted in the current minor cycle.")
-
- Closed
-
- relates to
-
-
- Closed
-