Jump to content

7 posts in this topic

Posted

[quote]The [url="https://code.google.com/p/zopfli/"]Zopfli Compression Algorithm[/url] is a new open sourced general purpose data compression library that got its name from a Swiss bread recipe. It is an implementation of the [url="https://en.wikipedia.org/wiki/DEFLATE"]Deflate[/url] compression algorithm that creates a smaller output size compared to previous techniques. The smaller compressed size allows for better space utilization, faster data transmission, and lower web page load latencies. Furthermore, the smaller compressed size has additional benefits in mobile use, such as lower data transfer fees and reduced battery use. The higher data density is achieved by using more exhaustive compression techniques, which make the compression a lot slower, but do not affect the decompression speed. The exhaustive method is based on iterating entropy modeling and a shortest path search algorithm to find a low bit cost path through the graph of all possible deflate representations.

The output generated by Zopfli is typically [url="https://zopfli.googlecode.com/files/Data_compression_using_Zopfli.pdf"]3

Share this post


Link to post
Share on other sites

Posted

Interesting. Wonder how it does against LZMA and LZMA2 considering both reasonable speed and compression ratio.

Share this post


Link to post
Share on other sites

Posted

[quote]Zopfli is bit-stream compatible with compression used in gzip, Zip, PNG, HTTP requests, and others.[/quote]
i wonder how it goes against stuff like KZIP & PNGOUT ?
[url="http://advsys.net/ken/utils.htm"]http://advsys.net/ken/utils.htm[/url]

Share this post


Link to post
Share on other sites

Posted

[quote name='UXGaurav' post='595553310']Wonder how it does against LZMA and LZMA2 considering both reasonable speed and compression ratio.[/quote]This is about DEFLATE-compatible compressions, so LZMA/LZMA2 don't enter into the picture.

[spoiler]But yes, LZMA/LZMA2 [i]traditionally[/i] has superior compression ratio. Too bad that still not used in HTTP transfer-encoding.[/spoiler]

Share this post


Link to post
Share on other sites

Posted

I read the PDF. It's decent, but has a very specific use case. That is: One-time compression and multiple decompressions for static data (they do acknowledge this). Compressing files using this algo is epic slow compared to gzip for the same file (talking 5 seconds for gzip compared to 7 minutes for the same file using Zopfli). It'll be very good for conserving bandwidth on, say, file distribution sites though where CPU time is inconsequential compared to bandwidth requirements.
1 person likes this

Share this post


Link to post
Share on other sites

Posted

Some good stuff coming out of Google labs these days.
1 person likes this

Share this post


Link to post
Share on other sites

Posted

^ Maybe Microsoft can steal it. :p

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.