-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GC processing seems not working well #311
Comments
@zhenyun , can you add more details please? Sample log if possible with data/results. Also if there are multiple problems, please open multiple issues. |
Is this for JDK 8? Does naarad work fine for you with the log in examples/log/ directory? |
it works with examples/log/gc.log, but that gc.log does not have some values, eg. Allocation failures. |
I used this (shortened) gc.log:
In naarad output, the following pauses are not identified: |
The wildcard is to cover ParNew GC pause, not for the concurrent mode failure. From: Richard Hsu <[email protected]mailto:[email protected]> Concurrent mode failure seems to be coinciding with Allocation Failure in the format. So I think we should be covered. #300#300 will add support for this and we've asked @alfhhttps://github.com/alfh to update so that the regex is a wildcard for "GC (*)" so it looks like it'd catch your three examples. — |
I saw there are four active pull requests from @alfh which may potentially fix this issue. |
GC output is incorrect; GC log has many "concurrent mode failure" pauses, but they are not captured in naarad output.
The text was updated successfully, but these errors were encountered: