Google Launches Brotli, a New Open Source Compression Algorithm For the Web

Mark Wilson writes: As websites and online services become ever more demanding, the need for compression increases exponentially. Fans of Silicon Valley will be aware of the Pied Piper compression algorithm, and now Google has a more efficient one of its own. Brotli is open source and is an entirely new data format that offers 20-26 percent greater compression than Zopfli, another compression algorithm from Google. Just like Zopfli, Brotli has been designed with the internet in mind, with the simple aim of making web pages load faster. It is a "lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods". Compression is better than LZMA and bzip2, and Google says that Brotli is "roughly as fast" as zlib's Deflate implementation.

Comments

A better idea

[Anonymous Coward]

If they want to make webpages load quicker, remove ads.

Re:A better idea

[Anonymous Coward]

If they want to make webpages load quicker, remove ads.

That would only be a linear improvement. They need to load exponentially faster.

Binary Page Delivery

[Anonymous Coward]

for a better user experience. The real reason is so that ad blockers will no longer work. It will no longer be web "pages", they will be "apps". The walled garden will move to the web and have the doorway sealed shut.

Re:Open Source Compression Algorithm For the Cows

[Anonymous Coward]

OOoops. Forgot to check the Anonymous checkbox again, sexconker? I think we know who the cow troll is. Now it is time to delete his account.

To make web pages load faster:

[Anonymous Coward]

Stop making my browser run 500 trips to DNS in order to run 500 trips to every ad server in the world.

Also, for the everloving sake of Christ, you don't need megabytes of scripts, or CSS, or any other shit loaded from 50 more random domains in order to serve up an article consisting of TEXT. One kilobyte of script will be permitted to setup a picture slideshow, if desired. /Get off my e-lawn

Re:7zip

[Anonymous Coward]

7z is pretty slow. Modern internet connection speeds are already between 100 Mbps (mobile) to up to 1 Gbps (fiber optics). Of course developing countries are still at about 50-100 Mbps level.

Thus something like LZ4 compresses much less, but total time of transmission is typically better. Who cares of the compression ratio, total time to complete the transaction matters.

1997 called

[Intrepid imaginaut]

It wants its bottleneck back. From what I can see it's plugins, scripts and adverts loading from fifty different sites that clog web pages, not large file sizes or what have you. Yes I get that compression is vital for an outfit like Google and they want to showcase what they've been doing but most websites don't have their traffic volume.

Re:1997 called

[Ravaldy]

Websites maybe, web applications are a different story. Problem is that businesses make heavy use of web applications and data lists can grow out of control quickly if you include the formatting required to make it look right. One could say that these web application have bad data presentation strategies and I would argue that you'd probably be right in many cases. Unfortunately not all problems can be solved with forced filters and paging.

Take /. for example. The HTML alone of this page (with very few comments at this point) is 200KB. If you add up the CSS and JS you are well above 1MB. Data alone would probably take only 100KB but data that's hard to decipher through is not fun data hence the overhead.

Compression is a no brainer if used properly. Bandwidth is limited and so is processing power. Just a matter of deciding which one is more important at any given time.

As opposed to...

[JustAnotherOldGuy]

It is a "lossless compressed data format..."

As opposed to what, a lossy compression formula for data?

Well hell, if you don't need the original data back I've got a compressor algorithm that'll reduce a 50GB file to 1 byte every time. Sometimes even less than a byte, like maybe 0.25 bytes. In fact it reduces the file to such a small size that just finding it again turns out to be a real challenge...