From: Kris Van Bruwaene <Kris.VanBruwaene@vrt.be>
To: Nikita Danilov <Nikita@namesys.com>
Cc: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: Can compression at filesystem level improve overall performance?
Date: Mon, 22 Mar 2004 09:01:28 +0100 [thread overview]
Message-ID: <405E9D58.6080404@vrt.be> (raw)
In-Reply-To: <16475.9613.375262.677576@laputa.namesys.com>
Nikita Danilov wrote:
>Redeeman writes:
> > On Fri, 2004-03-19 at 15:25, Erik Terpstra wrote:
> > > Is it fair to say that today compression at the filesystem level would
> > > improve overall performance?
> > the more agressive you compress it the more cpu it takes, and that will
> > make it slower, but i think a small compression algorithm for filesystem
> > purpose could be written... however, i doubt it will be worth it,
> > harddrives are really cheap nowadays.. but maybe some algortihm to
> > compress cleartext only, or something..
>
>That's common misconception. :)
>
>The goal of compression is to conserve disk bandwidth rather than space.
>
>By compressing it is possible to transfer data (== uncompressed data
>user works with), at a rate higher than raw device bandwidth.
>
>
Something else to consider: the gain might not be so impressive, since
many files are already heavily compressed: apart from the obvious ones
(.zip .gz .bz2) most audio (.mp3) and video is natively compressed
(mpeg2/4), and amy office files as well (presentations, pdf...).
next prev parent reply other threads:[~2004-03-22 8:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 14:25 Can compression at filesystem level improve overall performance? Erik Terpstra
2004-03-19 16:29 ` Redeeman
2004-03-19 16:53 ` Nikita Danilov
2004-03-21 14:29 ` Sean Johnson
2004-03-21 23:17 ` Can compression at filesystem level improve overall The Amazing Dragon
2004-03-21 23:23 ` Sean Johnson
2004-03-22 9:14 ` Hans Reiser
2004-03-22 8:01 ` Kris Van Bruwaene [this message]
2004-03-22 18:00 ` Can compression at filesystem level improve overall performance? Scott Young
2004-03-22 20:04 ` Hans Reiser
2004-03-23 3:03 ` Scott Young
2004-03-23 10:59 ` Hans Reiser
2004-03-24 16:19 ` Scott Young
2004-03-29 5:25 ` Tom Vier
2004-03-29 5:16 ` Tom Vier
2004-03-30 3:34 ` Scott Young
2004-03-30 4:53 ` Tom Vier
2004-03-31 4:51 ` Scott Young
2004-04-08 21:46 ` Tom Vier
2004-04-08 11:47 ` Stewart Smith
2004-03-19 18:59 ` Hans Reiser
2004-03-23 0:17 ` Miguel
[not found] <no.id>
2004-03-24 0:08 ` The Amazing Dragon
2004-03-24 0:12 ` Alan Horn
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=405E9D58.6080404@vrt.be \
--to=kris.vanbruwaene@vrt.be \
--cc=Nikita@namesys.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.