All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hugo Chevrain <hugochevrain@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [RFB] add LZ4 compression method to btrfs
Date: Thu, 16 Feb 2012 13:07:29 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120216T135449-686@post.gmane.org> (raw)
In-Reply-To: 4F3BECE3.1080905@gmail.com

You're right about the broken links, my bad.


The first link related to a few statements by Mark Ruijter, copy/pasted below :

> I just looked into it and it appears to be promising. 
> On average the speeds appear to be 48% faster then snappy.
> This is amazing since snappy has proved to be 30% faster then QuickLZ 
> which once was the fastest compression protocol.

==> http://www.lessfs.com/wordpress/?p=684#comments

> I did not test LZ4 on high end hardware yet. 
> However even on my laptop it is clear that LZ4 does outperform snappy. 
> With the hardware being the bottleneck 
> LZ4 still manages to speed things up by 2~5%. 
> Most likely the difference will be larger when fast hardware is used

==> http://www.lessfs.com/wordpress/?p=688

There is no precise benchmark though. Just this sentence :

> I will post the exact performance numbers on low and high end hardware 
> after testing has finished.

So maybe someone has to ask Mark about these results.


The second link initially linked to Hadoop, which recently decided to integrate
LZ4 compression :
==> https://issues.apache.org/jira/browse/HADOOP-7657

However, since then, i've discovered the website of the developper in charge of
this patch (Binglin Chang), and he has come nice comparison figures available.
The main summary is copy/pasted below :

> Perf.RawCompressionLZ4    Block size: 64K
> Compress:  428M/s Decompress:   681M/s( 1584M/s) ratio: 43.0% - Total

> Perf.RawCompressionSnappy Block size: 64K
> Compress:  400M/s Decompress:   442M/s(  979M/s) ratio: 45.2% - Total

==> https://github.com/decster/jnicompressions/blob/master/README.md



      reply	other threads:[~2012-02-16 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 19:03 [RFB] add LZ4 compression method to btrfs David Sterba
2012-02-13 19:05 ` [PATCH 1/4] btrfs: prepare incompat flags for more compression methods David Sterba
2012-02-13 19:05   ` [PATCH 2/4] btrfs: add LZ4 compression method David Sterba
2012-02-13 19:05   ` [PATCH 3/4] btrfs: lz4: add wrapper for context size estimation David Sterba
2012-02-13 19:05   ` [PATCH 4/4] btrfs: lz4: add wrapper functions and enable it David Sterba
2012-02-14 20:44 ` [RFB] add LZ4 compression method to btrfs Markus Lindberg
2012-02-14 21:13   ` Andi Kleen
2012-02-14 21:47   ` Hugo Chevrain
2012-02-15 17:23     ` Kok, Auke-jan H
2012-02-15 17:35       ` Fahrzin Hemmati
2012-02-16 13:07         ` Hugo Chevrain [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20120216T135449-686@post.gmane.org \
    --to=hugochevrain@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.