-
Bug
-
Resolution: Fixed
-
P3
-
hs25
-
b35
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8016391 | 8 | Stefan Karlsson | P3 | Resolved | Fixed | b94 |
While investigating JDK-8015268, I found that a large portion of the young GC times where spent in the single-thread phase that prunes the StringTable (where interned Strings are registered).
This phase walks the StringTable twice. First to unlink all dead Strings and then to to update the references to all live Strings.
By simply combining these walks I could get a 10% decrease in young GC times on CRM Sales Opty.
This phase walks the StringTable twice. First to unlink all dead Strings and then to to update the references to all live Strings.
By simply combining these walks I could get a 10% decrease in young GC times on CRM Sales Opty.
- backported by
-
JDK-8016391 Large performance hit when the StringTable is walked twice in Parallel Scavenge
-
- Resolved
-
- is blocked by
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
JDK-8015237 Parallelize string table scanning during strong root processing
-
- Resolved
-