Closed bholdt closed 1 year ago
I have run a bunch of performance benchmarks. The ZSTD.decompress method with byte arrays was a lot faster than the ZSTD decompress with ByteBuffers.
It's because the ByteBuffer implementation allocates another ZSTD Frame Decompressor every time it decompresses.
This PR uses the already existing ZSTDFrameDecompressor instead of allocating a new one for every decompression.
:warning: 7 God Classes were detected by Lift in this project. Visit the Lift web console for more details.
I have run a bunch of performance benchmarks. The ZSTD.decompress method with byte arrays was a lot faster than the ZSTD decompress with ByteBuffers.
It's because the ByteBuffer implementation allocates another ZSTD Frame Decompressor every time it decompresses.
This PR uses the already existing ZSTDFrameDecompressor instead of allocating a new one for every decompression.