From: Hans Reiser <reiser@namesys.com>
To: Erik Terpstra <erik@solidcode.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Can compression at filesystem level improve overall performance?
Date: Fri, 19 Mar 2004 21:59:57 +0300 [thread overview]
Message-ID: <405B432D.5020305@namesys.com> (raw)
In-Reply-To: <405B02ED.4010602@solidcode.net>
Erik Terpstra wrote:
> Hello everyone,
>
> For the last couple of years I noticed that the performance of most of
> my systems has it's bottleneck in data throughput rather than CPU
> performance.
>
> Is it fair to say that today compression at the filesystem level would
> improve overall performance?
>
> If this is the case, it probably wouldn't be too hard to implement as
> a module in Reiser4?
>
> Any thoughts?
>
> --Erik.
>
>
We are working on it. Actually, it is hard to code because we need to
compress at flush to disk time rather than at each write. Flush related
plugins are the hardest plugins.
--
Hans
next prev parent reply other threads:[~2004-03-19 18:59 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 ` Can compression at filesystem level improve overall performance? Kris Van Bruwaene
2004-03-22 18:00 ` 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 [this message]
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=405B432D.5020305@namesys.com \
--to=reiser@namesys.com \
--cc=erik@solidcode.net \
--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.