I did not understand your remark about benchmarks. The recycling strategies
are there mostly to address memory concerns, not performance. For instance,
thread-locals are not a preferable option for apps that run on hundreds of
threads, which is the case in most Tomcat apps. Or am I missing a point
I like the idea, but I defer to the benchmark results for this sort of thing ;-)
The ability to bound reusable objects below the thread count will become more
valuable when project loom[1] is released, as the JVM will support millions of
virtual threads on a handful of OS threads. This will make
Hello,
As you might have already known, JSON template layout uses RecyclerFactory
for recycling objects to maintain a certain memory footprint, that is, work
garbage-free. By default there are 3 recycler factory implementations
shipped: dummy, thread-local, and queue. (See the relevant part of the
