From: Hans Reiser <reiser@namesys.com>
To: Clay Barnes <clay.barnes@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Compression Plugin
Date: Tue, 06 Jun 2006 12:19:41 -0700 [thread overview]
Message-ID: <4485D54D.30606@namesys.com> (raw)
In-Reply-To: <433017C1.4050408@gmail.com>
Clay Barnes 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? I know that compression of files like bz2 will vary (in
>that they'll be essentially uncompressed) from source/text files
>(excellent compression). A rough estimate from someone's experience
>using on mixed files it would help.
>
>Also: Is the algorithm set in stone? If so what is it? If not, what
>is it now/expected to be?
>
>
It is lzo1. There are multiple compression algorithms to choose from,
one of them is gzip (more cpu but better compression). lzo1 gets > 50%
on text and executables and nothing on mp3s and video.
>Thanks,
>Clay Barnes
>
>
>
>
next prev parent reply other threads:[~2006-06-06 19:19 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
2006-06-06 19:19 ` Hans Reiser [this message]
-- 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=4485D54D.30606@namesys.com \
--to=reiser@namesys.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.