JDK-7143511 : G1: Another instance of high GC Worker Other time (50ms)
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8-pool
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2012-02-07
- Updated: 2013-09-18
- Resolved: 2012-04-11
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | Other |
|---|---|---|
7u40Fixed  |
8Fixed |
hs24Fixed |
Description
At a G1 performance meeting with the some SPARC hardware engineers, the SPARC engineers showed some G1 GC logs where the time attibuted to "GC Worker Other" time was much higher than expected (around 50ms). I believe the benchmark being run was SPECjbb2012 - but I don't have details of the VM flags they were running with. The system they were running on was, I believe, a T4. The SPARC engineers offered some collect experiements from the affected runs - which should help us track down this particular instance of the issue. We have seen this issue before and the "Other" time was coming from the freeing Chunks associated with the resource allocations. The resource allocations were coming resource-allocating a closure while scanning a card during RSet scanning. We were resource-allocating a new closure per card scanned.
Comments
|