All of lore.kernel.org
 help / color / mirror / Atom feed
From: PFC <lists@boutiquenumerique.com>
To: reiserfs-list@namesys.com
Subject: Re: Compression Plugin
Date: Wed, 21 Sep 2005 10:33:30 +0200	[thread overview]
Message-ID: <op.sxf114l4th1vuj@localhost> (raw)
In-Reply-To: <433102D0.7010706@mch.one.pl>


>>> An interesting idea:  select the algo and a range of compression
>>> levels per file,

	A simple check on wether it's an already compressed file (using file  
extension and magic number) should be quite easy to do and cheap.

	Now, intrigued by this lzo thingie, I ran a little benchmark on my emails  
; I have a huge mail spool and my mail client is always slow to launch...
	Seems that on this laptop LZO can compress about 40 MB/s and decompress  
about 200 (!) MB/s. On the mail spool, compression ratio was about 1/2 ;  
gzip was better, although 5-6 times slower. So considering the disk  
throughput is only 15 MB/s, this could make it twice as fast with CPU to  
spare. Yowza !

>>> 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.
>>   Kinda makes it sound like in addition to the "repacker" that repacks
>> blocks in order and squeezes them, (which should allow for filesystem
>> size reduction), there'll be a compression repacker too that allows
>> you to repack files to a higher or lower compression level (anyone
>> remember the Compression Agent that came with DoubleSpace and the like
>> in Windows 9x?).
>
> AFAIR e2compr patch to ext2 (which enables compression on a ex2  
> filesystem) could use many packing methods, including gzip and bzip2  
> (!), with a range from 1 to 9...
>
> I certainly could imagine cases where compression level is more  
> important than speed.
>
>



  reply	other threads:[~2005-09-21  8:33 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 [this message]
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=op.sxf114l4th1vuj@localhost \
    --to=lists@boutiquenumerique.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.