ZXC
github.comKey Features
Tech Stack
Key Features
Tech Stack
Huh? This is exactly what lz4 does. Yes, zxc is faster than lz4 at decompressing, but lz4 is clearly asymmetric in the benchmarks shown further down on the page.
My phrasing was a bit too binary. What I meant to highlight is that ZXC pushes this trade-off much further than LZ4. I designed ZXC specifically for scenarios where we accept a significantly slower build-time/compression cost in exchange for that extra raw decode throughput.
I built ZXC, a lossless compression library designed specifically for "Write Once, Read Many" scenarios (Game assets, Firmware, App bundles).
The Concept: Standard real-time codecs (LZ4, Snappy) are designed for symmetry. ZXC explores an asymmetric approach: it spends significantly more CPU cycles at compression time to generate a bitstream specifically structured for modern, wide-issue execution pipelines (maximizing Instruction Level Parallelism).
Performance (Verified via lzbench integration): ZXC was merged into the official lzbench repository monday.
ARM64 (Apple M2): 6,365 MB/s decoding (~40% faster than LZ4). x86_64 (AMD EPYC 9554): At Level 5, ZXC achieves compression ratios comparable to zstd --fast while maintaining nearly 2x the decompression speed (3.8 GB/s vs 2.0 GB/s).
Implementation Details: Written in C99, zero internal allocation (caller provides buffers). Designed for easy FFI (Go/Python/Rust bindings). Validated via continuous fuzzing (ClusterFuzzLite) and static analysis. PR for OSS-Fuzz integration is ready.
This is a v0.1.1 release. The bitstream format is stable but open to improvements based on feedback from the community.
lzbench has added ZXC to its suite. This makes a nice apples to apples comparison possible.
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.