Files
cpp-project-template/third_party/zlib-ng/test/benchmarks
tqcq 68b2e7f763
Some checks failed
sm-rpc / build (Debug, arm-linux-gnueabihf) (push) Successful in 1m34s
sm-rpc / build (Debug, aarch64-linux-gnu) (push) Successful in 2m46s
sm-rpc / build (Debug, host.gcc) (push) Failing after 1m28s
sm-rpc / build (Release, aarch64-linux-gnu) (push) Successful in 2m14s
sm-rpc / build (Release, arm-linux-gnueabihf) (push) Successful in 2m8s
sm-rpc / build (Debug, mipsel-linux-gnu) (push) Successful in 5m35s
sm-rpc / build (Release, host.gcc) (push) Failing after 1m55s
sm-rpc / build (Release, mipsel-linux-gnu) (push) Successful in 7m21s
fix: breakpad use miniz
2025-08-25 15:24:22 +08:00
..
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00
2025-08-25 15:24:22 +08:00

Benchmarks

These benchmarks are written using Google Benchmark.

Repetitions

To increase the number of times each benchmark iteration is run use:

--benchmark_repetitions=20

Filters

To filter out which benchmarks are performed use:

--benchmark_filter="adler32*"

There are two different benchmarks, micro and macro.

Benchmark benchmark_zlib

These are microbenchmarks intended to test lower level subfunctions of the library.

Benchmarks include implementations of: - Adler32 - CRC - 256 byte comparisons - SIMD accelerated "slide hash" routine

By default these benchmarks report things on the nanosecond scale and are small enough to measure very minute differences.

Benchmark benchmark_zlib_apps

These benchmarks measure applications of zlib as a whole. Currently the only examples are PNG encoding and decoding. The PNG encode and decode tests leveraging procedurally generated and highly compressible image data.

Additionally, a test called png_decode_realistic that will decode any RGB 8 BPP encoded set of PNGs in the working directory under a directory named "test_pngs" with files named {0..1}.png. If these images do not exist, they will error out and the benchmark will move on to the next set of benchmarks.

benchmark_zlib_apps_alt

The user can compile a comparison benchmark application linking to any zlib-compatible implementation of his or her choosing.