All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: Clay Barnes <clay.barnes@gmail.com>, reiserfs-list@namesys.com
Subject: Re: Compression Plugin
Date: Tue, 20 Sep 2005 18:36:14 -0400	[thread overview]
Message-ID: <e692861c05092015364a887a44@mail.gmail.com> (raw)
In-Reply-To: <43307E49.8060404@slaphack.com>

On 9/20/05, David Masover <ninja@slaphack.com> wrote:
> Probably lzo, which is already used for other things like network
> connections (ssh, openvpn, and so on).  The nice thing about lzo is that
> it's fast, faster than gzip or bzip2, and gets decent compression -- not
> great, but decent.  I don't usually get gzip or bzip2 to compress at
> disk speed, but then, I usually crank the compression way up, so YMMV.
> The point of using a fast algorithm is that you not only save space, but
> when you apply it to things like text files, it can actually make things
> go faster.
> 
> But I imagine it will be settable per-file.  Files can be both encrypted
> and compressed, and I think (I hope) it could be with a choice of
> crypto/compression algorithms.

I didn't know SSH supported LZO.  Rsync does though...

Gzip compression is pretty darn quick at lower levels, though
depending on the lz77 implimentaiton it can be fairly slow at higher
compression levels.

An interesting idea:  select the algo and a range of compression
levels per file, but select the actual compression level at flush time
based on some estimate of how loaded the system is.. :)
Probably not worth it even though the amount of compression and the
speed differ greatly from -1 to -9... I hope no one wastes their time
on it until the more important things are done.. but perhaps a nice
touch.

  reply	other threads:[~2005-09-20 22:36 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 [this message]
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
  -- 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=e692861c05092015364a887a44@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=clay.barnes@gmail.com \
    --cc=ninja@slaphack.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.