From: "Jose R. Santos" <jrs@us.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: seekwatcher IO visualization
Date: Thu, 9 Aug 2007 22:01:11 -0500 [thread overview]
Message-ID: <20070809220111.24d782cd@gara> (raw)
In-Reply-To: <20070809205355.GB6689@schatzie.adilger.int>
On Thu, 9 Aug 2007 14:53:55 -0600
Andreas Dilger <adilger@clusterfs.com> wrote:
> I saw on #linuxfs today some graphs and movies by Chris Mason showing
> the poor IO locality for ext3 compared to btrfs and XFS. It would be
> interesting to run this with ext4+mballoc+delalloc, and a separate
> one with the FLEXBG feature enabled to see how that improves the
> seeking/locality.
>
> http://oss.oracle.com/~mason/seekwatcher/
>
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
>
I was planing to use seekwatcher to look at fsck activity when using
FLEX_BG since I'm already seeing noticeable improvements by using this
feature alone.
We can try other workloads and see how ext4 compares.
-JRS
prev parent reply other threads:[~2007-08-10 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 20:53 seekwatcher IO visualization Andreas Dilger
2007-08-10 3:01 ` Jose R. Santos [this message]
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=20070809220111.24d782cd@gara \
--to=jrs@us.ibm.com \
--cc=adilger@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).