-
Enhancement
-
Resolution: Fixed
-
P4
-
11, 17, 18, 19
-
b04
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8306809 | 17.0.8 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
Our support engineers asked this:
> I see these G1Concurrent safepoints in JDK17:
> [0.064s][info][safepoint ] Safepoint "G1Concurrent", Time since last: 1666947 ns, Reaching
safepoint: 79150 ns, At safepoint: 349999 ns, Total: 429149 ns
> I've always thought that "concurrent" and "safepoint" are basically antonyms.
> What is a G1Concurrent safepoint? How can a concurrent event require a safepoint?
I think the naming here is unfortunate:
https://github.com/openjdk/jdk/blob/b79554bb5cef14590d427543a40efbcc60c66548/src/hotspot/share/gc/g1/g1VMOperations.hpp#L89-L103
...and we can clean that up a bit. I'll propose a patch.
> I see these G1Concurrent safepoints in JDK17:
> [0.064s][info][safepoint ] Safepoint "G1Concurrent", Time since last: 1666947 ns, Reaching
safepoint: 79150 ns, At safepoint: 349999 ns, Total: 429149 ns
> I've always thought that "concurrent" and "safepoint" are basically antonyms.
> What is a G1Concurrent safepoint? How can a concurrent event require a safepoint?
I think the naming here is unfortunate:
https://github.com/openjdk/jdk/blob/b79554bb5cef14590d427543a40efbcc60c66548/src/hotspot/share/gc/g1/g1VMOperations.hpp#L89-L103
...and we can clean that up a bit. I'll propose a patch.
- backported by
-
JDK-8306809 G1: Rework VM_G1Concurrent VMOp to clearly identify it as pause
-
- Resolved
-
