JDK-8240679 introduced a change where the information exposed via the GarbageCollectorMXBean went from being related to the GC pauses to instead be related to the GC cycles. This helped provide more accurate heap usage information. However, some users have noticed that that you no longer get timing information related to the GC pauses, only related to the GC cycle.
Shenandoah has opted for having two distinct memory managers to provide timing information about both pauses and cycles. To align how concurent GCs report this information, ZGC should probably do the same. Testing: * Tier1-7 with ZGC * Manual testing with relevant jtreg tests ------------- Commit messages: - 8265136: ZGC: Expose GarbageCollectorMXBeans for both pauses and cycles Changes: https://git.openjdk.java.net/jdk/pull/3483/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=3483&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8265136 Stats: 179 lines in 9 files changed: 107 ins; 25 del; 47 mod Patch: https://git.openjdk.java.net/jdk/pull/3483.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/3483/head:pull/3483 PR: https://git.openjdk.java.net/jdk/pull/3483
