Implement CMS log parser. #22
Assignees
Labels
Comments
ducky-hong
pushed a commit
that referenced
this issue
May 12, 2016
ducky-hong
added a commit
that referenced
this issue
May 17, 2016
parboiled is PEG (Parsing Expression Grammar) implementation.
PEG is more concise than regex, and regex could not handle recursive
structure well.
GcEventNode is added to access the parsed data easily. Its concrete class is
generated by Auto Value library which utilizes annotation processing. IDE setup
is required and the instruction can be found here:
google/auto#106
|
Need to parse CMS-concurrent events. |
xeoh
pushed a commit
that referenced
this issue
May 18, 2016
[#22] Implemented simple CMS gc logs parser
xeoh
pushed a commit
that referenced
this issue
May 22, 2016
[#22] Implemented simple CMS gc logs parser
|
@ducky-hong Can I close this issue? |
|
CMS-concurrent events are not added yet. After that, we could close this issue. |
ducky-hong
added a commit
that referenced
this issue
Jun 1, 2016
- CMS_CONCURRENT LogType added on gc_model. - CMS concurrent cpu time, wall time added. - Avoid potential NPE on CmsLogParser#parseGcEvent.
ducky-hong
added a commit
that referenced
this issue
Jun 2, 2016
[#22] Add CMS-concurrent-* gc events parsing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GCTool aims to parse CMS logs only.
Following link is useful to understand CMS logs.
https://blogs.oracle.com/poonam/entry/understanding_cms_gc_logs
The text was updated successfully, but these errors were encountered: