Splitting NMT memory counters into "live" and "flat" classes

[Robert Toyonaga]

Hi Everyone,

What are your thoughts on splitting the NMT memory counter classes (both
MemoryCounter and VirtualMemory) into "live" and "flat" classes? Currently,
the counters are used for both recording live data and for storing static
data when creating reports. However, after snapshotting the counters for
report generation, we no longer need atomic operations or any updating of
peak values. The "live" set of classes could keep the atomic operations,
peak updating, setters, and snapshotting functionality. The "flat" classes
could get rid of atomic, peak updating, and only need getters.

The JBS issue for this is JDK-8334234

Thanks!
Robert Toyonaga
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/serviceability-dev/attachments/20240829/14bc68d9/attachment.htm>