rounding error in logs

[Kirk Pepperdine]

Hi Thomas,

Thanks for this. I don’t see CR JDK-8058221 showing up so it’s difficult to comment. What you’ve mentioned is ok but I think it would be nice is the logs used the same formatting string.

BTW, my comment on reporting in bytes still stands.. it would eliminate the need for any formatting! Just print longs ;-)

Regards,
Kirk

On Sep 11, 2014, at 1:24 PM, Thomas Schatzl <thomas.schatzl at oracle.com> wrote:

> Hi Kirk,
> 
> On Mon, 2014-09-08 at 11:28 +0200, Kirk Pepperdine wrote:
>> 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.
> 
> While it reads 7740M as initial heap occupancy here, I created a CR
> "JDK-8058221 - Rounding in log output makes evaluation difficult" as
> this is something that is something that regularly poses an issue.
> 
> Please comment if the CR is appropriate.
> 
> Thanks,
>  Thomas
> 
> 
> 

-------------- 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/20140912/c9e8c457/signature.asc>