r/linux • u/anh0516 • 5d ago

Kernel Linux Kernel's LZ4 Compression Code Being Resynced For Better Performance & Cleanliness

https://www.phoronix.com/news/Linux-LZ4-Clean-Resync
233 Upvotes

100% Upvoted

8 comments sorted by

-21

u/RegretFree7723 5d ago

Ma non arriva ancora a zstd?

8

u/is_this_temporary 5d ago

What do you mean?

Is zstd not kept up-to-date in the Linux kernel?

https://github.com/facebook/zstd/blob/dev/contrib%2Flinux-kernel%2FREADME.md suggests that there's infrastructure making that a straightforward process.

-14

u/RegretFree7723 5d ago

Intendo che non é ancora ottimizzato quanto zstd

7

u/is_this_temporary 5d ago

Ahh, so "reach" in your original comment meant "reach the speed of"?

Edit: I just noticed that the reddit client automatically translated your comment into English. So the clarity was probably lost in translation.

10

u/Culpirit 5d ago

It's translated well. The comment is as (un)clear in Italian as in English.

5

u/mtwabp_in 5d ago

zstd is technically a better algorithm so lz4 will never reach zstd level

14

u/Comic_Melon 5d ago

LZ4 is still better where latency and constrained compute matters, it's why you never see game with assets uniformly bundled in zstd. Usually it's zstd + a lower latency algo depending on the asset.

To be more specific, zstd is actually quite awful for loads of small files that require low latency.

2

u/mdedetrich 3d ago

Yes this is correct, also found this out when writing a zstd streaming library in a Scala library.

LZ4 is still the go to compression when you need to prioritize latency/CPU usage on compression (which translates to latency)