Repository navigation
Benchmarking
The published report is bench/linux-x86-avx2. It compares zipir with the fastest single-threaded tools on one Linux x86-64 host (AMD Ryzen 9 3950X, AVX2), on sequencing, mass spectrometry, and general corpus files, for every format zipir writes and reads.
- Whole commands. Each sample is a complete process: start-up, reading the input, and writing the output. This is what a user running the command sees, not a library inner loop.
- Matched rounds. Every tool for one file and operation runs in the same interleaved rounds, so load on the machine slows all of them alike. Times are medians of 25 rounds.
- Correctness before timing. Every tool is checked against an independent decoder before it is timed, and every compressed output is decoded again during the run.
- Speed and size together. A faster compressor often writes larger files, so every compression result shows both.
- Memory. Peak resident memory of the whole process.
zipir holds each stream in one fixed workspace, so its peak stays near 0.6 MiB on every path and every file. The Zig standard library, also a static Zig program, lands at the same place but takes two to six times as long; part of the gap to the C tools is their libc runtime, not only their codec state.
zlib-ng, ISA-L igzip, the Zig standard library, and htslib bgzip built with libdeflate and with zlib-ng, each single-threaded, at the levels the report lists. The preset frontier figures add every level of libdeflate's own command.
The report predates 0.2.0's code: its zipir compression rows were measured at commit 5f25547 and its decompression rows at ff8e9e8. A matched run of the same peers on the small files at the release code showed decompression faster and gzip, zlib, and raw DEFLATE compression a few percent slower, the cost of making every compressor a std.Io.Writer. Compressed bytes did not change.
The comparison tools live in tools/: installing the peers, fetching the corpus, checking every peer's output, and timing with Zebrac 0.6.2. Their README gives the commands and how long each run takes. Timing needs Linux x86-64.