From: Zach Brown <zach.brown@oracle.com>
To: Daniel Phillips <phillips@google.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Another ocfs2 performance bug
Date: Fri, 10 Mar 2006 16:44:21 -0800 [thread overview]
Message-ID: <44121D65.5010004@oracle.com> (raw)
In-Reply-To: <4411FE80.7030302@google.com>
> Reading all the files in a big directory tree takes at least four times
> as long on ocfs2 as ext3.
> real 1m54.933s <===
> real 0m23.899s <===
Can you doctor your scripts to show@least some overview of the IO
patterns? Just the amount of reads and writes would be a good start,
but something like graphing blktrace output would be wildly instructive.
My first guess would be the known difference between OCFS2's full-block
inodes and ext3's habit of packing lots of inode structs into a block.
Secondary guesses would be lack of directory read-ahead, bad IO patterns
based on allocation policy, etc..
- z
WARNING: multiple messages have this Message-ID (diff)
From: Zach Brown <zach.brown@oracle.com>
To: Daniel Phillips <phillips@google.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] Another ocfs2 performance bug
Date: Fri, 10 Mar 2006 16:44:21 -0800 [thread overview]
Message-ID: <44121D65.5010004@oracle.com> (raw)
In-Reply-To: <4411FE80.7030302@google.com>
> Reading all the files in a big directory tree takes at least four times
> as long on ocfs2 as ext3.
> real 1m54.933s <===
> real 0m23.899s <===
Can you doctor your scripts to show at least some overview of the IO
patterns? Just the amount of reads and writes would be a good start,
but something like graphing blktrace output would be wildly instructive.
My first guess would be the known difference between OCFS2's full-block
inodes and ext3's habit of packing lots of inode structs into a block.
Secondary guesses would be lack of directory read-ahead, bad IO patterns
based on allocation policy, etc..
- z
next prev parent reply other threads:[~2006-03-11 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 22:32 [Ocfs2-devel] Another ocfs2 performance bug Daniel Phillips
2006-03-10 22:32 ` Daniel Phillips
2006-03-11 0:44 ` Zach Brown [this message]
2006-03-11 0:44 ` [Ocfs2-devel] " 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=44121D65.5010004@oracle.com \
--to=zach.brown@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=phillips@google.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.