From: Chris Mason <chris.mason@oracle.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Compressor options and speed vs size tradeoff.
Date: Mon, 09 Feb 2009 10:16:38 -0500 [thread overview]
Message-ID: <1234192598.1262.13.camel@think.oraclecorp.com> (raw)
In-Reply-To: <e692861c0902090023v42104857p47058f13829686be@mail.gmail.com>
On Mon, 2009-02-09 at 03:23 -0500, Gregory Maxwell wrote:
> I ran across an interesting page which reviews the performance of a
> number of compressors which are already available for the Linux Kernel
> (zlib, lzop, lzma) and which shows the highest performing compressor
> choice given the authors test CPU for a variety of data transfer
> rates, and read vs write ratio.
>
> http://users.elis.ugent.be/~wheirman/compression/
>
>
> It shows that for normal disk speeds (i.e. >200mbit/sec) LZOP of some
> flavor will yield the greatest performance.
>
> (LZMA, however, has considerably greater space savings; but isn't
> likely to increase overall performance with normal disk)
The compression metadata has what it needs to understand other
compression algorithms, but we haven't gotten around to actually coding
in support for other ones.
>From a latency point of view, the decompression speed matters most, but
both compression and decompression are done in the background by a
number of async helper threads in the kernel.
So, lots of the smaller differences between the compression algos end up
hidden for most users. I'm definitely not saying zlib is the perfect
compression routine, but it holds up well overall.
-chris
prev parent reply other threads:[~2009-02-09 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 8:23 Compressor options and speed vs size tradeoff Gregory Maxwell
2009-02-09 15:16 ` Chris Mason [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=1234192598.1262.13.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=gmaxwell@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox