Hi Richard,


I maintain hw-apex-bench (Apache-2.0), a small benchmark that measures the cost of reading one region of a compressed file — latency and decoded bytes — at different block sizes, for xz, zstd seekable and BGZF. Disclosure: I build it with heavy help from AI tools; every number is reproducible from the repository.


The nbdkit-xz-filter man page suggests many small blocks (16 MiB in its example) for random access. Would a table of region-read latency and ratio versus xz block size, measured on a public VM disk image, be useful to you or to users choosing --block-size? If so, which image and read sizes would you consider representative?


That is the whole question — "not useful" is a fine answer too.


Thanks,

Yakiv Shavidze

https://github.com/yasha1971-coder/hw-apex-bench