From: Andrew Morton <akpm@digeo.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Shawn Starr <spstarr@sh0n.net>,
sct@redhat.com, Con Kolivas <conman@kolivas.net>,
linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] EXT3 vs EXT2 results with rmap14a and testing with contest 0.34
Date: Wed, 18 Sep 2002 23:32:19 -0700 [thread overview]
Message-ID: <3D896F73.5D1265B5@digeo.com> (raw)
In-Reply-To: 20020919061301.GB13929@clusterfs.com
Andreas Dilger wrote:
>
> ...
> > Kernel Time CPU
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d 325.39 82%
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d 411.47 64%
>
> I don't see this as hugely surprising. ext3 uses more CPU than ext2.
> If you are using up the CPU doing other things, then naturally ext3
> will take a longer wall-clock time to complete the same tasks as ext2.
Yup. But here the CPU load is less; obviously some more seeking
was done. That's fairly normal for ext3 - it has to write the journal
as well as the filesystem....
> I know that Andrew has been doing a bunch of work to reduce ext3 CPU
> usage/locking/etc., but I think that is all in 2.5 kernels.
>
I had a little patch. Stephen is working on the big fix.
next prev parent reply other threads:[~2002-09-19 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 1:18 EXT3 Testing w/ rmap14a with contest results Shawn Starr
2002-09-19 3:10 ` Andrew Morton
2002-09-19 2:16 ` Shawn Starr
[not found] ` <200209182140.30364.spstarr@sh0n.net>
[not found] ` <1032403983.3d893c0f8986b@kolivas.net>
2002-09-19 4:16 ` [BENCHMARK] EXT3 vs EXT2 results with rmap14a and testing with contest 0.34 Shawn Starr
2002-09-19 4:21 ` Shawn Starr
2002-09-19 6:13 ` Andreas Dilger
2002-09-19 5:44 ` Shawn Starr
2002-09-19 6:32 ` Andrew Morton [this message]
2002-09-23 19:03 ` Stephen C. Tweedie
2002-09-23 20:00 ` Shawn Starr
2002-09-23 20:05 ` Andrew Morton
2002-09-23 20:22 ` Stephen C. Tweedie
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=3D896F73.5D1265B5@digeo.com \
--to=akpm@digeo.com \
--cc=adilger@clusterfs.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=spstarr@sh0n.net \
/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.