Przemyslaw Skibinski

I implemented this but it looks overwhelming: ``` memcpy = memcpy, threading=external_pool brieflz = brieflz 1.3.0; supported levels=[1-9], threading=external_pool brotli = brotli 1.1.0; supported levels=[0-11], threading=external_pool brotli22 = brotli 1.1.0...

This looks better: ``` memcpy = memcpy; threading=-T brieflz = brieflz 1.3.0; levels=[1-9]; threading=-T brotli = brotli 1.1.0; levels=[0-11]; threading=-T brotli22 = brotli 1.1.0 -d22; levels=[0-11]; threading=-T brotli24 = brotli...

The list shows what options are supported by given compressors in lzbench. For different reasons -T is disabled for crush, glza, tornado, yappy.

It doesn't matter if an option is provided by bench or codec itself. I wan't to know what options are supported for each codec. But OK, let's start without `threading=-T`:...

Hi, what compilation error do you see? I compiled lzbench with ``` make CC=gcc-14 CXX=g++-14 -j40 CUDA_BASE="" DONT_BUILD_LIZARD=1 ``` and compilation was fine without lizard. I verified it looking at...

@stima Please contribute your CMake for lzbench. It should be helpful for many people.

Thanks for a fix. Probably some AWS/GCP instance with a gfx card is required to test lzbench with CUDA. But just building may be possible.

For developers interested in using bzip3 as a compression library through its API, the lack of built-in multithreading can be a significant drawback. As shown above, well-established compressors such as...

I decided to remove code that fixes issues with incompressible data for many compressors because it showed memcpy speed instead of real speed or an error. Incompressible data should be...

Lzbench reserves now `input_size + input_size/8 + 1024` bytes of memory for output buffer where `input_size` is a file size or a block size: https://github.com/inikep/lzbench/blob/master/bench/lzbench.h#L26 In case of some simple...