Sanmayce_Kaze

Let's dramatize the next 2 scenarios:

- 10Mbps or 1MB/s connection;

- 100Mbps or 10MB/s connection.

The goal is to receive in our browser those 812,392,384 bytes as quickly as possible, in first case the winner is 77,286,010 bytes compressor, in second the winner is 90,239,627 bytes compressor, yes?

In first case transfer_time + decompression_time = 77s + 7s = 84s

In second case transfer_time + decompression_time = 9s + 1s = 10s

Now, you see that even in Web Browsing scenario the best performer is not established, right?

You miss the point, your list is meaningful only in general compression cases, the Brotli thread (where we are) is all about boosting textual decompression while having/exploiting little resources (RAM mostly) as in the cases of Web Browsers.

As one (Jyrki) of co-authors commented: ``` For more clarity on the situation, you could compare LZMA, LZHAM and brotli at the same decoding memory use. Possibly values between 1-4 MB (window size 20-22) are the most relevant for the HTTP content encoding. Unlike in a compression benchmark, there are a lot of other things going on in a browser, and the allocated memory at decoding time is a critically scarce resource. ``` Source: http://google-opensource.blogspot.bg/2015/09/introducing-bro...

Thanks, yes, very good roster, I am aware of these performers, maybe out there some hidden excellent tight/fast ones exist?!

In my view the two best are:

169,476,113 bytes, 2.072 sec., 0.352 sec., lz4 -9

115,985,847 bytes, 386.192 sec., 0.850 sec., lzturbo -39 -p1 -b4

LzTurbo benefits a lot from bigger blocks, in above example it uses 4MB block single-threadedly, and look how fast it is, if 16 threads are to be used what the outcome would be ... maybe 0.100 sec?!

I have an actual question. Who can name all the decompressors that outperform Brotli both in compression ratio and decompression speed? As I see it, that's the ultimate goal, to boost I/O via transparent decompression.

Reading the PDF paper I see they use for benchmarking Xeon with price-tag in range of $560, how this can be reconciled with hot phrases like boosting browsing on mobile devices?!