From: Valerie Clement <valerie.clement@bull.net>
To: Alex Tomas <alex@clusterfs.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Bad performance results with the latest git patches
Date: Fri, 07 Sep 2007 14:24:47 +0200 [thread overview]
Message-ID: <46E1430F.3050702@bull.net> (raw)
Hi Alex,
running ffsb tests (large files creation) on my system with the latest
ext4 git patches against a 2.6.23-rc4 kernel, I've got very bad
performance results: the I/O throughput measured on an ext4 filesystem
is ten times lower than those measured on an XFS filesystem on the same
machine.
I have mounted the ext4 filesytem with mballoc, delalloc and
data=writeback options.
dmesg output shows plenty of error messages like this:
EXT4-fs error (device sdc): ext4_ext_search_right: bad header in inode
#3745797: unexpected eh_depth - magic f30a, entries 81, max 84(0), depth
0(1)
EXT4-fs error (device sdc): ext4_ext_search_right: bad header in inode
#3745797: unexpected eh_depth - magic f30a, entries 81, max 84(0), depth
0(1)
EXT4-fs error (device sdc): ext4_ext_search_right: bad header in inode
#3745797: unexpected eh_depth - magic f30a, entries 81, max 84(0), depth
0(1)
EXT4-fs error (device sdc): ext4_ext_search_right: bad header in inode
#3745797: unexpected eh_depth - magic f30a, entries 81, max 84(0), depth
0(1)
If I removed the second call to ext4_ext_check_header() in the
ext4_ext_search_right() function, the problem disappears, no more error
messages and better throughput values close to those measured on the XFS
filesystem.
It seems that the depth value passed in argument is buggy.
In a previous line,
while (++depth < path->p_depth) {
the depth value is incremented even if we don't enter the loop. Is it
the problem ?
Could you check this?
Thanks,
Valérie
next reply other threads:[~2007-09-07 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 12:24 Valerie Clement [this message]
2007-09-07 21:37 ` Bad performance results with the latest git patches Andreas Dilger
2007-09-10 10:14 ` Aneesh Kumar K.V
2007-09-10 11:39 ` Valerie Clement
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=46E1430F.3050702@bull.net \
--to=valerie.clement@bull.net \
--cc=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).