Dmitry Konstantinov 05b7af7ae4 Propagate ref to pool thread cache down in the allocation stack to avoid extra thread local lookup (#10166) ... Motivation: PoolChunk requires a link to a PoolThreadCache to init ByteBuf. Currently the link is retrieved from a thread local: arena.parent.threadCache(). It has some performance cost. At the beginning of the allocation call the PoolThreadCache is already retrieved from the thread local. The reference can be propagated through the calls and used. Modifications: Replace second lookup of PoolThreadCache during ByteBuf init by propagation of a reference to PoolThreadCache down in the allocation stack explicitly Result: Improve performance of ByteBuf allocation --Before-- Benchmark (size) (tokens) (useThreadCache) Mode Cnt Score Error Units SimpleByteBufPooledAllocatorBenchmark.getAndRelease 123 0 true avgt 20 57.112 ± 1.004 ns/op SimpleByteBufPooledAllocatorBenchmark.getAndRelease 123 100 true avgt 20 222.827 ± 1.307 ns/op --After-- Benchmark (size) (tokens) (useThreadCache) Mode Cnt Score Error Units SimpleByteBufPooledAllocatorBenchmark.getAndRelease 123 0 true avgt 20 50.732 ± 1.321 ns/op SimpleByteBufPooledAllocatorBenchmark.getAndRelease 123 100 true avgt 20 216.892 ± 3.806 ns/op		2020-04-06 08:01:01 +02:00
..
main	Propagate ref to pool thread cache down in the allocation stack to avoid extra thread local lookup (#10166)	2020-04-06 08:01:01 +02:00
test/java/io/netty/buffer	FixedCompositeByteBuf.isDirect() may return wrong value when constructed with empty array (#10005)	2020-02-08 17:05:26 +01:00