rounding error in logs

[Kirk Pepperdine]

Hi,

I’ve got this from a 1.8.0_20 log but it’s been around for some time.

[Eden: 448.0M(448.0M)->0.0B(448.0M) Survivors: 64.0M->64.0M Heap: 7740.7M(15.0G)->7334.2M(15.0G)]
15116.779: [GC cleanup 7334M->6817M(15G), 0.0181473 secs]

As you can see the occupancy before collection is reported as 7334M where as the occupancy after collection in the summary record is 7334.2M.

In this case the collections are less than 5ms apart which means that the .2M discrepancy would appear to be a rounding error due to the precision of how values are being reported. I briefly looked JDK code and it seems as if EXT_SIZE_FORMAT	 is being used in the initial summary but construction/printing the GC cleanup seems to be delegated to VMThread and it’s not using the same format.

On a side note, simply reporting in bytes would be a nice step in simplifying things.

Kind regards,
Kirk Pepperdine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20140908/c4764440/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20140908/c4764440/signature.asc>