3 ms·
> Due to the amount of CPU time required — 2 to 3 orders of magnitude more than zlib at maximum quality — Zopfli is best suited for applications where data is c
by rtkwe 14y ago
> Due to the amount of CPU time required — 2 to 3 orders of magnitude more than zlib at maximum quality — Zopfli is best suited for applications where data is compressed once and sent over a network many times, for example, static content for the web.
So it's not a magic bullet, and only results in 3-8 percent shrink compared the zlib at maximum compression. It is interesting that it is able to be decompressed by existing algorithms, which means it can be rolled out immediately instead of waiting for it to be adopted by enough browsers to make the compression time investment useful.
Google's blog post is here: http://googledevelopers.blogspot.com.es/2013/02/compress-data-more-densely-with-zopfli.html http://googledevelopers.blogspot.com.es/2013/02/compress-dat...
- gillianseed 14y agoWell it uses the same deflate algorithm which is used by zlib, gzip etc. There are many much more capable compression algorithms which will get much better results with alot less cpu time (lzma comes to mind), however the big deal is that deflate is supported by all browsers and thus it is a standarized means of compressing content. With that, being able to squeeze out 3-8% more compression for compressed web content can likely be attractive if it is a decent part of your bandwidth usage.