netty5/codec
Norman Maurer b14dfbb74c
FastLzFrameDecoder should use allocator to allocate output buffer (#11499)
Motivation:

FastLzFrameDecoder currently not use the allocator to alocate the output buffer. This means that if you use the PooledByteBufAllocator you still can't make use of the pooling. Beside this the decoder also does an uncessary memory copy when no compression is used.

Modifications:

- Allocate the output buffer via the allocator
- Don't allocate and copy if we handle an uncompressed chunk
- Make use of ByteBufChecksum for a few optimizations when running on a recent JDK

Result:

Less allocations when using FastLzFrameDecoder
2021-07-21 22:09:12 +02:00
..
src FastLzFrameDecoder should use allocator to allocate output buffer (#11499) 2021-07-21 22:09:12 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2021-07-16 06:23:23 +00:00