From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Fw: Re: ICP, 3ware, Areca?
Date: Tue, 7 Nov 2006 17:20:11 -0500 [thread overview]
Message-ID: <20061107222011.GH29071@ti64.telemetry-investments.com> (raw)
In-Reply-To: <20061107134513.fbd5f219.akpm@osdl.org>
On Tue, Nov 07, 2006 at 01:45:13PM -0800, Andrew Morton wrote:
> On Tue, 07 Nov 2006 14:59:52 -0600
> Dave Kleikamp <shaggy@linux.vnet.ibm.com> wrote:
>
> > On Tue, 2006-11-07 at 11:47 -0800, Andrew Morton wrote:
> > > Why is ext3 slow??
> >
> > Allocation? I don't see anything indicating that Bill is overwriting an
> > existing file, so there is block allocation and journaling overhead. If
> > that's the case, it would be interesting to see how fast ext3 is when
> > overwriting a file. Extents and delayed allocation should improve on
> > this a lot.
Will do.
> Maybe. or perhaps some funniness with RAID aligment.
I neglected to include the relevant RAID/mkfs info here.
device=/dev/sdc2 # ought to have been on a raid stripe boundary
# very close to the start of the array
# XFS:
mkfs.xfs -f -d su=65536,sw=6 -l su=65536 $device
mount -o noatime,attr2,largeio,logbsize=64k $device /mnt
# Ext3: XFS has problems up through 2.6.18-rc5; use slow, but safe, Ext3:
mke2fs -j -J size=400 -E stride=96 $device
mount -o noatime $device /mnt
Also, I ran blockdev --flushbufs and
echo 1 | sudo tee /proc/sys/vm/drop_caches
before each test.
-Bill
prev parent reply other threads:[~2006-11-07 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 19:47 Fw: Re: ICP, 3ware, Areca? Andrew Morton
2006-11-07 19:55 ` Alex Tomas
2006-11-07 20:59 ` Dave Kleikamp
2006-11-07 21:06 ` bzzz
2006-11-07 21:45 ` Andrew Morton
2006-11-07 22:07 ` Bill Rugolsky Jr.
2006-11-07 22:20 ` Bill Rugolsky Jr. [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=20061107222011.GH29071@ti64.telemetry-investments.com \
--to=brugolsky@telemetry-investments.com \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.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