linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Starr <spstarr@sh0n.net>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: sct@redhat.com, akpm@digeo.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: Thu, 19 Sep 2002 01:44:20 -0400	[thread overview]
Message-ID: <200209190144.20212.spstarr@sh0n.net> (raw)
In-Reply-To: <20020919061301.GB13929@clusterfs.com>

Well, all the tests were done in single user mode =)

On September 19, 2002 02:13 am, Andreas Dilger wrote:
> On Sep 19, 2002  00:16 -0400, Shawn Starr wrote:
> > These results compare EXT3 against EXT2 with rmap using the contest tool
> > you can get it at: http://contest.kolivas.net
> >
> > These tests are from a Athlon MP 2000+ w/ 512MB RAM
> >
> > noload:
> >
> > Kernel					Time            	CPU
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            259.47		99%
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            267.66          	97%
> >
> > process_load:
> >
> > Kernel                  			Time            	CPU
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            318.91          	80%
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            324.44          	79%
> >
> > io_halfmem:
> >
> > Kernel                  			Time			CPU
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            306.82          	87%
> > 2.4.20-pre7-rmap14a-xfs-uml-shawn12d            461.74          	57%
> >
> > io full mem:
> >
> > 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.
>
> 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.
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-09-19  6:39 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 [this message]
2002-09-19  6:32         ` Andrew Morton
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=200209190144.20212.spstarr@sh0n.net \
    --to=spstarr@sh0n.net \
    --cc=adilger@clusterfs.com \
    --cc=akpm@digeo.com \
    --cc=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.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;
as well as URLs for NNTP newsgroup(s).