Search papers, labs, and topics across Lattice.
This paper investigates the factors influencing decode throughput in the ACEAPEX LZ77 format, revealing that work granularity, specifically average match length, is the primary determinant of throughput rather than traditional metrics like occupancy or parallelism. Through extensive testing on an NVIDIA H100, the authors demonstrate a significant 3.5x throughput increase as the average match length is increased from 32 to 1024 bytes. Importantly, they establish that optimizing the minimum match length on the encode side can enhance both compression ratio and decode throughput across multiple datasets without altering the decode kernel.
Increasing the minimum match length can simultaneously boost both compression efficiency and decode speed, achieving up to a 78% throughput increase without any kernel modifications.
The ACEAPEX line of work established a lossless LZ77 format whose back-references are absolute output positions, giving parallel, compressed-resident GPU decode with sub-millisecond region seek. What it did not establish is what governs the decode throughput of such a format, or how to improve it. This paper answers both. Through controlled ablations on an NVIDIA H100 we show that decode throughput is governed not by occupancy, compute, address scatter, or launch parallelism, but by work granularity: throughput is a function of the average match length, because a short match leaves most lanes of a cooperating warp idle. A synthetic copy kernel confirms a 3.5x throughput span (212 to 744 GB/s) as average match length grows from 32 to 1024 bytes. Real data sit at the low end (mean match length 6.5 on enwik9, 10.1 on FASTQ). We then show that this mechanism yields a practical, encode-side lever: raising the minimum match length by distance class (6/8/10/12 to 12/16/24/32) improves both compression ratio and decode throughput simultaneously on all eight tested datasets, with no exceptions and no change to the decode kernel. FASTQ decode rises from 142.6 to 178.6 GB/s while ratio improves 1.8%; enwik9 throughput rises 78%. This is not a trade-off: both gains follow from one cause, removing short matches whose far offsets cost more entropy than they save. All figures are bit-perfect (FNV on GPU paths, byte compare on CPU paths) and git-verifiable. Scope is explicit: figures are match-phase, device-resident; entropy and host transfer are outside the timer; seek is read/block-level, not coordinate-level; and we do not claim to exceed the hardware bandwidth ceiling.
