JEP 271: Unified GC Logging - First pre-review

[Kirk Pepperdine]

> 
> 1. Is there a specific reason to print the tag (gc) and other sub-tags in different order? For example, we have 'start, gc', and the order is different in 'gc, heap'.
>  [1.300s][info   ][start,gc    ] GC#3 GC (Allocation Failure) DefNew start
> [1.300s][info   ][start,gc    ] GC#4 Full GC (Allocation Failure) start
> [2.154s][info   ][gc          ] GC#4 Full GC (Allocation Failure) end 93M->59M(123M) (1.300s, 2.154s) 854.130ms
> [2.154s][info   ][gc,heap     ] GC#3 def new generation: 36767K->0K(39296K)
> [2.154s][info   ][gc,heap     ] GC#3 tenured generation: 58893K->61204K(87424K)
> [2.154s][info   ][gc,metaspace] GC#3 Metaspace: 2953K->2953K(1056768K)
>  <>if possible, I think we should have the order 'main-tag, sub-tag' at all the places.

Hi Poonam, I quite frankly, don’t see the need for the tags at all. They are quite redundant as the text is pretty clear as to what the line contains. In fact, unless there is some clear value in the annotations added by UL, I’ll be ignoring that chunk of text all together.

Regards,
Kirk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20151027/5dbfad82/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/20151027/5dbfad82/signature.asc>