-
Notifications
You must be signed in to change notification settings - Fork 576
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
Consider enabling verbose garbage collection by default #23001
Labels
Comments
Design Issues discussion outcomes:
|
The performance team ran startup, footprint, first request and throughput tests with and without verbosegc enabled using IBM Java (on both the latest Liberty and tWAS). None of the tests had more than 1% difference in performance, and most were less than 0.5% difference. Next step: discuss at the next Liberty Design Issues call. |
48 tasks
Delivered in #23607 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the use case that you want to enable:
Enable verbosegc by default
Describe why this is important to you:
By default, verbosegc is not enabled in Liberty (specifically, not enabled by default in Java). This is a problem if a performance or OutOfMemoryError issue occurs as the issue will often need to be reproduced with verbosegc, or users may simply overlook GC performance issues (e.g. thread dumps may point to various application stacks but the underlying issue could be GC).
Additional context
Draft UFO: https://ibm.box.com/s/u65i1hqmy7xyawppv1383x97jccud3es
The text was updated successfully, but these errors were encountered: