From: Gregory Maxwell <gmaxwell@gmail.com>
To: Clay Barnes <clay.barnes@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Compression Plugin
Date: Tue, 20 Sep 2005 17:53:01 -0400 [thread overview]
Message-ID: <e692861c05092014534d9bf66c@mail.gmail.com> (raw)
In-Reply-To: <433017C1.4050408@gmail.com>
On 9/20/05, Clay Barnes <clay.barnes@gmail.com> wrote:
> Forgive me if this has been answered recently, but I haven't gotten my
> last two dozen e-mails for today yet.
>
> Regarding the compression plugin, what sort of compression can one
> expect from it?
[snip]
Just a general, no reiser4 specifc answer since because the
compression isn't done yet I don't know the details on reiser4's
performance....
It is generally the case the disk based compression performs somewhat
worse than normal file based compressors. This is because every block
of data must be compressed alone in order to preserve the random
access semantics of the file system.
This also means that there is less to be gained by using alternative
compression systems (such as bzip2 or better LZMA) because most only
pick up their impressive performance as a result of having a much
larger context and at a greatly increased cost in memory usage.
For disk based compression Lz77 is pretty good and is so widely used
that people feel comfortable implimenting it in kernel space. Another
interesting player is LZO because decompression requires very little
memory and is VERY VERY fast (I think someting like 8x faster than
gzip in my testing). This means that decompression is effectively
free. However compression is perhaps 10% worse than LZ77 ... on most
hardware the disk is so slow that the decrease in compression
outweighs the improvement in decompression performance. But on systems
with a fast disk array, LZO may be a welcome tradeoff.
next prev parent reply other threads:[~2005-09-20 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 14:08 Compression Plugin Clay Barnes
2005-09-20 21:25 ` David Masover
2005-09-20 22:36 ` Gregory Maxwell
2005-09-21 1:51 ` michael chang
2005-09-21 6:50 ` Tomasz Chmielewski
2005-09-21 8:33 ` PFC
2005-09-21 17:31 ` Hans Reiser
2005-09-21 11:56 ` Edward Shishkin
2005-09-20 21:53 ` Gregory Maxwell [this message]
2006-06-06 19:19 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2006-05-26 21:18 reiser4progs+libaal 1.0.5 mail
2006-05-28 2:33 ` Compression Plugin Hönsch Roland
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=e692861c05092014534d9bf66c@mail.gmail.com \
--to=gmaxwell@gmail.com \
--cc=clay.barnes@gmail.com \
--cc=reiserfs-list@namesys.com \
/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.