Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please benchmark against latest zlib #4169

Open
Snowiiii opened this issue Oct 14, 2024 · 4 comments
Open

Please benchmark against latest zlib #4169

Snowiiii opened this issue Oct 14, 2024 · 4 comments
Assignees
Labels

Comments

@Snowiiii
Copy link

Hello, I saw that on the README there is a benchmark where zstd will be compared against zlib 1.2.11. I would appreciate if you would compare zstd against the latest zlib (1.3.1)

@Cyan4973 Cyan4973 self-assigned this Oct 14, 2024
@Cyan4973
Copy link
Contributor

We are using lzbench for the benchmarks,

the last commit of lzbench supports zlib v1.2.11,
which is directly bundled in the source tree.

The easiest solution for us would be for lzbench to update its support for zlib v1.3.1.
Then we could report the updated results.

From the changelog description, we don't anticipate any measurable performance difference between these 2 versions.
Mainly some bug fixes.

@Snowiiii
Copy link
Author

Hey, Thanks for the quick response. It looks like lzbench is dead tbh. We may should consider a different benchmarking tool

@Adenilson
Copy link

Details may be a bit hazy since it was way back in April 2022 (i.e. 2 years and 8 months ago) when I last measured, but I recall that zlib 1.2.12 featured a faster CRC-32 checksum using the Kadatch-Jenkins algorithm.

That helped performance in general in zlib, something like +30% faster decompression in canonical zlib (i.e. Mark Adler's zlib).

That being said, zstd should still be many times faster.

@Adenilson
Copy link

@op: Here some data comparing zlib 1.2.11 vs 1.2.12 (and 1.3 will feature the very same Kadatch-Jenkins CRC-32) running in a Xeon processor:
https://issues.chromium.org/issues/40050946#comment62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants