GCViewer icon indicating copy to clipboard operation
GCViewer copied to clipboard

PrintGCID not parsed

Open YouriAndropov opened this issue 7 years ago • 4 comments

Hi, I recently discovered a HotSpot diagnostic option, PrintGCID, with such outputs :

2018-05-06T02:54:06.938+0200: 5.970: #2: [GC concurrent-mark-end, 0.0018985 secs] 2018-05-06T02:54:06.938+0200: 5.970: #2: [GC remark 2018-05-06T02:54:06.938+0200: 5.970: #2: [Finalize Marking, 0.0002212 secs] 2018-05-06T02:54:06.938+0200: 5.971: #2: [GC ref-proc, 0.0002123 secs] 2018-05-06T02:54:06.938+0200: 5.971: #2: [Unloading, 0.0024467 secs], 0.0032812 secs] [Times: user=0.00 sys=0.00, real=0.00 secs] 2018-05-06T02:54:06.941+0200: 5.974: Total time for which application threads were stopped: 0.0033949 seconds, Stopping threads took: 0.0000471 seconds 2018-05-06T02:54:06.941+0200: 5.974: #2: [GC cleanup 11M->11M(1024M), 0.0008772 secs] [Times: user=0.22 sys=0.00, real=0.00 secs] 2018-05-06T02:54:06.942+0200: 5.975: Total time for which application threads were stopped: 0.0009325 seconds, Stopping threads took: 0.0000167 seconds (...) 2018-05-06T02:54:07.275+0200: 6.307: #3: [GC pause (G1 Evacuation Pause) (young) Desired survivor size 4718592 bytes, new threshold 15 (max 15)

Unfortunately, these ids are not parsed: AVERTISSEMENT [DataReaderSun1_6_0G1]: com.tagtraum.perf.gcviewer.imp.UnknownGcTypeException: Unknown gc type: '#' AVERTISSEMENT [DataReaderSun1_6_0G1]: com.tagtraum.perf.gcviewer.imp.UnknownGcTypeException: Unknown gc type: '#' AVERTISSEMENT [DataReaderSun1_6_0G1]: com.tagtraum.perf.gcviewer.imp.UnknownGcTypeException: Unknown gc type: '-' AVERTISSEMENT [DataReaderSun1_6_0G1]: com.tagtraum.perf.gcviewer.imp.UnknownGcTypeException: Unknown gc type: '#'

YouriAndropov avatar May 06 '18 00:05 YouriAndropov

Hi

Interesting - thank you for pointing this out! What JDK and what options did you use to create this output?

chewiebug avatar May 08 '18 20:05 chewiebug

Hello, I'm using the latest 1.8.0_172 oracle JDK, with the following logging options :

-verbose:gc -Xloggc:gc_jmeter_%%p.log -XX:+PrintGCDetails -XX:+PrintGCCause -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCID -XX:+PrintGCTaskTimeStamps

YouriAndropov avatar May 09 '18 12:05 YouriAndropov

Thank you! I didn't know that diagnostic option for jdk8. Starting with jdk9 and java unified logging, I saw that id appear, as well. Seems to be a default option, then.

-------- Original Message -------- From: Ayoross [email protected] Sent: 9 May 2018 14:19:02 CEST To: chewiebug/GCViewer [email protected] Cc: chewiebug [email protected], Comment [email protected] Subject: Re: [chewiebug/GCViewer] PrintGCID not parsed (#197)

Hello, I'm using the latest 1.8.0,172 oracle JDK, with the following lgging options :

-verbose:gc -Xloggc:D:\Archives\Work\gc_jmeter_%%p.log -XX:+PrintGCDetails -XX:+PrintGCCause -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCID -XX:+PrintGCTaskTimeStamps

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/chewiebug/GCViewer/issues/197#issuecomment-387720084

chewiebug avatar May 13 '18 13:05 chewiebug

Hi @YouriAndropov

Please try it: https://github.com/chewiebug/GCViewer/pull/260

Thanks, Leslie Zhai

xiangzhai avatar Jul 28 '22 03:07 xiangzhai