From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Abhishek Rai <abhishekrai@google.com>,
Andreas Dilger <adilger@sun.com>,
linux-kernel@vger.kernel.org, Ken Chen <kenchen@google.com>,
Mike Waychison <mikew@google.com>
Subject: Re: [PATCH] Clustering indirect blocks in Ext3
Date: Fri, 16 Nov 2007 01:37:17 -0600 [thread overview]
Message-ID: <20071116073716.GB17536@waste.org> (raw)
In-Reply-To: <20071115230219.1fe9338c.akpm@linux-foundation.org>
On Thu, Nov 15, 2007 at 11:02:19PM -0800, Andrew Morton wrote:
> On Thu, 15 Nov 2007 21:02:46 -0800 "Abhishek Rai" <abhishekrai@google.com> wrote:
...
> > 3. e2fsck speedup with metaclustering varies from disk
> > to disk with most benefit coming from disks which have a large number
> > of indirect blocks. For disks which have few indirect blocks, fsck
> > usually doesn't take too long anyway and hence it's OK not to deliver
> > a huge speedup there. But in all cases, metaclustering doesn't cause
> > any degradation in IO performance as seen in the benchmarks above.
>
> Less speedup, for more-and-smaller files, it appears.
>
> An important question is: how does it stand up over time? Simply laying
> files out a single time on a fresh fs is the easy case. But what happens
> if that disk has been in continuous create/delete/truncate/append usage for
> six months?
Try Chris Mason's compilebench, which is a decent aging simulation.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-11-16 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 5:02 [PATCH] Clustering indirect blocks in Ext3 Abhishek Rai
2007-11-16 7:02 ` Andrew Morton
2007-11-16 7:37 ` Matt Mackall [this message]
2007-11-18 15:52 ` Abhishek Rai
2007-11-18 20:47 ` Matt Mackall
2007-11-19 10:34 ` Kyungmin Park
2007-11-20 20:25 ` John Stoffel
2007-11-16 11:28 ` Andreas Dilger
2007-11-16 21:11 ` Theodore Tso
2007-11-17 0:25 ` Abhishek Rai
2007-11-17 2:58 ` Theodore Tso
2007-11-17 8:58 ` Abhishek Rai
2007-12-21 14:15 ` Abhishek Rai
2008-01-10 21:17 ` Abhishek Rai
2008-01-11 17:05 ` Daniel Phillips
2008-01-12 0:04 ` Andrew Morton
2008-01-12 6:05 ` Daniel Phillips
2008-01-13 5:06 ` Abhishek Rai
2007-11-16 22:27 ` Abhishek Rai
[not found] <9q1CT-82L-3@gated-at.bofh.it>
[not found] ` <9q3v2-2Br-3@gated-at.bofh.it>
[not found] ` <9qgLE-7ds-21@gated-at.bofh.it>
[not found] ` <9qjJx-3wE-9@gated-at.bofh.it>
[not found] ` <9qm4D-70Q-1@gated-at.bofh.it>
[not found] ` <9CQTt-7cr-27@gated-at.bofh.it>
[not found] ` <9KcYS-46E-27@gated-at.bofh.it>
2008-01-11 14:12 ` Bodo Eggert
2008-01-11 14:49 ` Abhishek Rai
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=20071116073716.GB17536@waste.org \
--to=mpm@selenic.com \
--cc=abhishekrai@google.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox