From: Johannes Stezenbach <js@linuxtv.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Suparna Bhattacharya <suparna@in.ibm.com>,
Andrew Morton <akpm@osdl.org>, Willy Tarreau <w@1wt.eu>,
Linus Torvalds <torvalds@osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>,
git@vger.kernel.org, nigel@nigel.suspend2.net,
"J.H." <warthog9@kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
webmaster@kernel.org,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: How git affects kernel.org performance
Date: Mon, 8 Jan 2007 14:41:47 +0100 [thread overview]
Message-ID: <20070108134147.GB5291@linuxtv.org> (raw)
In-Reply-To: <20070108125819.GA32756@thunk.org>
On Mon, Jan 08, 2007 at 07:58:19AM -0500, Theodore Tso wrote:
>
> The fastest and probably most important thing to add is some readahead
> smarts to directories --- both to the htree and non-htree cases. If
> you're using some kind of b-tree structure, such as XFS does for
> directories, preallocation doesn't help you much. Delayed allocation
> can save you if your delayed allocator knows how to structure disk
> blocks so that a btree-traversal is efficient, but I'm guessing the
> biggest reason why we are losing is because we don't have sufficient
> readahead. This also has the advantage that it will help without
> needing to doing a backup/restore to improve layout.
Would e2fsck -D help? What kind of optimization
does it perform?
Thanks,
Johannes
next prev parent reply other threads:[~2007-01-08 13:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061216094421.416a271e.randy.dunlap@oracle.com>
[not found] ` <20061216095702.3e6f1d1f.akpm@osdl.org>
[not found] ` <458434B0.4090506@oracle.com>
[not found] ` <1166297434.26330.34.camel@localhost.localdomain>
[not found] ` <1166304080.13548.8.camel@nigel.suspend2.net>
[not found] ` <459152B1.9040106@zytor.com>
[not found] ` <1168140954.2153.1.camel@nigel.suspend2.net>
[not found] ` <45A08269.4050504@zytor.com>
[not found] ` <45A083F2.5000000@zytor.com>
[not found] ` <Pine.LNX.4.64.0701062130260.3661@woody.osdl.org>
[not found] ` <20070107085526.GR24090@1wt.eu>
2007-01-07 9:15 ` How git affects kernel.org performance Andrew Morton
2007-01-07 9:38 ` Rene Herman
2007-01-08 3:05 ` Suparna Bhattacharya
2007-01-08 12:58 ` Theodore Tso
2007-01-08 13:41 ` Johannes Stezenbach [this message]
2007-01-08 13:56 ` Theodore Tso
2007-01-08 13:59 ` Pavel Machek
2007-01-08 14:17 ` Theodore Tso
2007-01-08 13:43 ` Jeff Garzik
2007-01-09 1:09 ` Paul Jackson
2007-01-09 2:18 ` Jeremy Higdon
[not found] ` <20070109075945.GA8799@mail.ustc.edu.cn>
2007-01-09 7:59 ` Fengguang Wu
2007-01-09 7:59 ` Fengguang Wu
2007-01-09 7:59 ` Fengguang Wu
2007-01-09 16:23 ` Linus Torvalds
[not found] ` <20070110015739.GA26978@mail.ustc.edu.cn>
2007-01-10 1:57 ` Fengguang Wu
2007-01-10 1:57 ` Fengguang Wu
2007-01-10 1:57 ` Fengguang Wu
2007-01-10 3:20 ` Nigel Cunningham
[not found] ` <20070110140730.GA986@mail.ustc.edu.cn>
2007-01-10 14:07 ` Fengguang Wu
2007-01-10 14:07 ` Fengguang Wu
2007-01-10 14:07 ` Fengguang Wu
2007-01-12 10:54 ` Nigel Cunningham
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=20070108134147.GB5291@linuxtv.org \
--to=js@linuxtv.org \
--cc=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=randy.dunlap@oracle.com \
--cc=suparna@in.ibm.com \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
--cc=warthog9@kernel.org \
--cc=webmaster@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).