-
-
Notifications
You must be signed in to change notification settings - Fork 793
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
Allow pluggable buffer recycling via new RecyclerPool
extension point
#1089
Comments
Note: #1064 is the current PR for implementation |
Created issues for follow-up work for 4 modules:
planning to at least tackle first 2 for 2.16, but ideally all 4. |
Ok, realized that JAX-RS / Jakarta RS use case is NOT for Object recycling, so not related to this work -- closed issues. Smile format use case removed altogether as FasterXML/jackson-dataformats-binary#403 (performance benefit seemed too modest to be worth it). This leaves just Avro to be converted, hopefully by 2.16.0. |
BufferRecyclerPool
extension pointRecyclerPool
extension point
Although the current hard-coder
ThreadLocal
-based buffer recycling (viaBufferRecycler
containers accessed viaBufferRecyclers
) has worked reasonably well up until recently, changes to later JVMs have madeThreadLocal
access less beneficial; and in near future (Project Loom et al) even counter-productive.But there are other ways to allow beneficial buffer recycling: especially for use cases where pooling is integrated with other frameworks.
To allow new default and alternative recycling schemes, let's add
RecyclerPool
extension point, make current implementation work with it.And for bonus points, possibly implement one or more alternate implementations to use.
The text was updated successfully, but these errors were encountered: