BufferRecycler
should avoid setting replacement if one already returned, bigger
#1186
Labels
2.17
Issues planned (at earliest) for 2.17
performance
Issue related to performance problems or enhancements
(based on discussion FasterXML/jackson#204 -- good suggestion by @kkkkkhhhh)
It seems that
BufferRecycler
will always replace assigned buffer when release method is called. But it would probably make sense to only replacenull
or smaller buffer, and avoid replacing bigger buffer with smaller.While in the original expected usage sequence should always be "alloc / release / allow / release" (in which case "release" would be replacing
null
), there can be cases where this does not hold (multiple parsers/generators per thread, concurrently; but also just parser-and-generator case).So let's add some basic checking into release method.
The text was updated successfully, but these errors were encountered: