-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add more instrumentation to ArrayByteBufferPool
and improve its eviction algorithm
#11375
Conversation
instrument ArrayByteBufferPool acquisition sizes Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could these stats be collected in a ByteBufferPool wrapper?
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
ArrayByteBufferPool
ArrayByteBufferPool
and improve its eviction algorithm
@gregw unfortunately, most of those stats are about exposing internal stuff, so it's hard to have them in a wrapper. But I moved the most expensive ones (the requested sizes) to another |
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Note that all the |
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
…tty-12-more-instrumentation
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
…pt memory Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Superseded by #11400 |
The current info reported in
ArrayByteBufferPool
's dump is too limited, this is an attempt at improving that.This could help with issues like #11326 as we may better understand the state of the pool when it reaches a problematic point.
Also, the eviction algorithm was reworked to fix its most glaring problems.