From: Daniel Phillips <phillips@google.com>
To: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Another ocfs2 performance bug
Date: Fri, 10 Mar 2006 14:32:32 -0800 [thread overview]
Message-ID: <4411FE80.7030302@google.com> (raw)
Hi guys,
Reading all the files in a big directory tree takes at least four times
as long on ocfs2 as ext3.
# ocfs2: Copy a kernel tree to /dev/null
mount -tocfs2 /dev/hdb /big
time find /big/linux-2.6.16-rc3 -type f -exec cp {} /dev/null \;
real 1m54.933s <===
user 0m0.896s
sys 0m1.844s
time find /big/linux-2.6.16-rc3 -type f -exec cp {} /dev/null \;
real 0m14.301s
user 0m5.172s
sys 0m9.093s
# ext3: Copy a kernel tree to /dev/null
mount -text3 /dev/hdb /big
time find /big/linux-2.6.16-rc3 -type f -exec cp {} /dev/null \;
real 0m23.899s <===
user 0m4.672s
sys 0m9.513s
time find /big/linux-2.6.16-rc3 -type f -exec cp {} /dev/null \;
real 0m14.198s
user 0m5.168s
sys 0m8.977s
Regards,
Daniel
next reply other threads:[~2006-03-10 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 22:32 Daniel Phillips [this message]
2006-03-11 0:44 ` [Ocfs2-devel] Another ocfs2 performance bug Zach Brown
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=4411FE80.7030302@google.com \
--to=phillips@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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