News for hackers. Stuff that matters.
Re:How LZ4 works (2016) by hedora on Sunday June 25, 2017 @11:38AM (#14630485)
This is true, there is low algorithmic novelty in lz4.

However, that's missing the point: lz4's decompressor is simultaneously simple and also the fastest thing aroud, at least at the moment.

In fact, it is so fast, it can be used to accelerate local data transfers over "slow" links like bonded 10GBit ethernet and arrays of PCIe SSD's.

Re:How LZ4 works (2016) by Darkenetor on Sunday June 25, 2017 @04:43PM (#14632059)
> lz4's decompressor is simultaneously simple and also the fastest thing aroud, at least at the moment

The proprietary LzTurbo [0] and free Lizard [1] both claim to be faster at decompression while having better compression ratios.

[0] https://github.com/powturbo/TurboBench

[1] https://github.com/inikep/lizard

Re:How LZ4 works (2016) by kzrdude on Sunday June 25, 2017 @11:52AM (#14630580)
Doesn't that also explain why it came later? The low compression ratio is useful nowadays, with large throughputs.
Re:How LZ4 works (2016) by hedora on Sunday June 25, 2017 @03:07PM (#14631582)
Maybe. It might just be that the tricks it plays matter a lot on newer CPUs, and older fast compressors played older tricks.

I think the ratio of CPU cycles to i/o bandwidth is what really matters. Presumably the optimal tradeoff between CPU throughout and compression ratios depends on that and varies over time.

Re:How LZ4 works (2016) by TheDong on Sunday June 25, 2017 @05:44PM (#14632364)
The low compression ratio / fast speed trade-off has always been valuable.

For example, block-level filesystem compression (what lz4 is used for with zfs) has been valuable for filesystems essentially forever.

There's always been a need for very high throughput on the local filesystem.