From: tridge@samba.org
To: Hans Reiser <reiser@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: performance of filesystem xattrs with Samba4
Date: Sat, 20 Nov 2004 10:01:33 +1100 [thread overview]
Message-ID: <16798.31565.306237.930372@samba.org> (raw)
In-Reply-To: <419E1297.4080400@namesys.com>
Hans,
I did some testing with reiser4 from 2.6.10-rc2-mm2. As far as I can
tell it doesn't seem to support the xattr calls (fsetxattr, fgetxattr
etc). Is that right, or did I miss a patch somewhere? The code seems
to set the xattr methods to NULL and has the prototypes #if'd out.
The result without xattr support was 52 MB/sec, which is a bit slower
than the reiser3 I tested in 2.6.10-rc2. For easy comparison, here are
the non-xattr results for the various filesystems I've tested:
tmpfs 69 MB/sec
ext2 68 MB/sec
ext3 67 MB/sec
xfs+2Kinode 63 MB/sec
xfs 62 MB/sec
reiser 58 MB/sec
reiser4 52 MB/sec (on a -mm2 kernel)
jfs 36 MB/sec
I used default options for mkreiser4, and default mount options. Can
you suggest some options to try or would you prefer to wait till I've
done the new dbench so you can try this more easily yourself? (you can
of course try installing Samba4 to test now, but its a fast moving
target and involves a lot more than just filesystem calls).
To make sure the problem wasn't some of the other patches in -mm2, I
reran the ext3 results on -mm2, and was surprised to find quite a
large improvement! ext3 got 73 MB/sec without xattr support. It oopsed
when I enabled xattr (I'm working with sct on fixing those oopses).
Once the oopses are fixed I'll rerun all the various filesystems with
-mm2 and see if it only improves ext3 or if it improves all of them.
Would anyone care to hazard a guess as to what aspect of -mm2 is
gaining us 10% in overall Samba4 performance?
Cheers, Tridge
next prev parent reply other threads:[~2004-11-19 23:06 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 [this message]
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
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=16798.31565.306237.930372@samba.org \
--to=tridge@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).