-
Type:
Enhancement
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 9
-
Component/s: hotspot
-
b51
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082863 | emb-9 | Claes Redestad | P4 | Resolved | Fixed | team |
| JDK-8086450 | 8u65 | Claes Redestad | P4 | Resolved | Fixed | b01 |
| JDK-8076065 | 8u60 | Claes Redestad | P4 | Resolved | Fixed | b09 |
| JDK-8137687 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
| JDK-8077465 | emb-8u60 | Claes Redestad | P4 | Resolved | Fixed | team |
On benchmarks with a large number of reference changes (like nosql benchmarks) on "large" machines we noticed that the HotCardCache_lock is highly contended(*).
Investigate and fix this in the hope to improve behavior.
(*) Contended as in at the time of trying to get ownership of the lock, there is already another owner of that lock.
Investigate and fix this in the hope to improve behavior.
(*) Contended as in at the time of trying to get ownership of the lock, there is already another owner of that lock.
- backported by
-
JDK-8076065 Decrease Hot Card Cache Lock contention
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-