From: Hans Reiser <reiser@namesys.com>
To: tridge@samba.org
Cc: linux-kernel@vger.kernel.org,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: performance of filesystem xattrs with Samba4
Date: Sat, 20 Nov 2004 22:11:39 -0800 [thread overview]
Message-ID: <41A0319B.7060803@namesys.com> (raw)
In-Reply-To: <16800.2371.421108.693783@samba.org>
tridge@samba.org wrote:
>
>So while I sympathise with you wanting reiser4 to be tuned for "big"
>storage, please remember that a good proportion of the installs are
>likely to be running "in-memory" workloads.
>
>
I agree that in-memory workloads are important, and that is why we
compress on flush rather than compressing on write for our compression
plugin, and it is why we should spend some time optimizing reiser4 to
make its code paths more lightweight for the in-memory case. At the
same time, I think that the workloads where the filesystem matters the
most are the ones that access the disk. With computers, in a large
percentage of the time that people notice themselves waiting, it is the
disk drive they are waiting on.
Sigh, there are so many things we should optimize for, and it will be
years before we have hit all the important ones.
next prev parent reply other threads:[~2004-11-21 6:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16759.16648.459393.752417@samba.org>
2004-10-21 18:32 ` [PATCH] Re: idr in Samba4 Jim Houston
2004-10-22 6:17 ` tridge
2004-11-19 7:38 ` performance of filesystem xattrs with Samba4 tridge
2004-11-19 8:08 ` James Morris
2004-11-19 10:16 ` Andreas Dilger
2004-11-19 11:43 ` tridge
2004-11-19 22:28 ` Andreas Dilger
2004-11-22 13:02 ` tridge
2004-11-22 21:40 ` Andreas Dilger
2004-11-19 12:03 ` Anton Altaparmakov
2004-11-19 12:43 ` tridge
2004-11-19 14:11 ` Anton Altaparmakov
2004-11-20 10:44 ` tridge
2004-11-20 16:20 ` Hans Reiser
2004-11-20 23:29 ` tridge
2004-11-19 15:34 ` Hans Reiser
2004-11-19 15:58 ` Jan Engelhardt
2004-11-19 22:03 ` tridge
2004-11-20 4:51 ` Hans Reiser
2004-11-19 23:01 ` tridge
2004-11-20 0:26 ` Andrew Morton
2004-11-21 1:14 ` tridge
2004-11-21 2:12 ` tridge
2004-11-21 23:53 ` tridge
2004-11-23 9:37 ` tridge
2004-11-23 17:55 ` Andreas Dilger
2004-11-24 7:53 ` tridge
2004-11-20 4:40 ` Hans Reiser
2004-11-20 6:47 ` tridge
2004-11-20 16:13 ` Hans Reiser
2004-11-20 23:16 ` tridge
2004-11-21 2:36 ` Hans Reiser
2004-11-21 0:21 ` tridge
2004-11-21 2:41 ` Hans Reiser
2004-11-21 1:53 ` tridge
2004-11-21 2:48 ` Hans Reiser
2004-11-21 3:19 ` tridge
2004-11-21 6:11 ` Hans Reiser [this message]
2004-11-21 22:21 ` Nathan Scott
2004-11-21 23:43 ` tridge
2004-12-03 17:49 Steve French
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=41A0319B.7060803@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-Dev@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tridge@samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox