Garbage Collection low-impact monitoring

[Ruben Badaró]

Hi,

I'm looking at ways of monitoring garbage collection statistics. My goals
are to have close to no impact to the running process and the most detail
possible. For that, I would like to avoid any type of instrumentation as I
want this running constantly in production.

An easy way is to parse gc logs but I remember someone reading the VM
structs for the garbage collection counters somewhere.
Do you guys have any examples of how to do this? I looked at the
Serviceability Agent but apparently it pauses the the running process while
inspecting. I was also considering (because my concern here is exclusively
when running Linux) to use the /proc/pid/maps memory mapped files and read
them in read-only mode from my monitoring process.
Does something like this already exist or is there a fundamental reason of
why it wouldn't work?

Thanks
Ruben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20130318/0ac04996/attachment.html