On Fri, Aug 07, 2026 at 10:09:46PM +0200, Tomas Vondra wrote: > FWIW I've tried with the 0001 part from the patch series in [1], which > reuses the zstd decompression context, and that significantly reduces > the difference between lz4 and zstd on the azure instances. > > i.e. ZSTD_createDCtx_internal disappears, which is ~9% of CPU time. > > I take this as a confirmation that most of the difference is indeed due > to the lower decompression speed.
Oh. We should definitely try something like that for v20. That makes sense for continuously decompressing sets of 8k pages. And the CCtx seems to be supported for quite some time (minimum version we require is 1.4, that has the CCtx things). Nice. > The question is what does this mean for this thread, i.e. for the > question what should 'on' translate to. I still think zstd seems like a > better default, despite this one result where lz4 does a bit better. > Especially if we know it the difference can be mostly eliminated. Thanks for all the benchmarks. Picking up a good default is hard, still I'd keep zstd as a better default choice overall, even after seeing these numbers. -- Michael
signature.asc
Description: PGP signature
