mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Cliff White <cliffw@osdl.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.0-test2-mm3 osdl-aim-7 regression
Date: Wed, 06 Aug 2003 12:10:34 -0700	[thread overview]
Message-ID: <200308061910.h76JAYw16323@mail.osdl.org> (raw)
In-Reply-To: Message from Andrew Morton <akpm@osdl.org>  of "Tue, 05 Aug 2003 22:23:54 PDT." <20030805222354.66dbdb8d.akpm@osdl.org>

> Cliff White <cliffw@osdl.org> wrote:
> >
> > 
> > I see 2.6.0-test2-mm4 is already in our queue, so this may be
> > Old News. ( serves me right for taking a weekend off )
> > Performance of -mm3 falls off on the 4-cpu machines. 
> > 
> > 2-cpu ssytems
> > Kernel 			JPM 
> > 2.6.0-test2-mm3		1313.53
> > linux-2.6.0-test2	1320.68 (0.54 % +)
> > 
> > 4-cpu systems
> > 2.6.0-test2-mm3		4824.96
> > linux-2.6.0-test2	5381.20 ( 11.53 % + )
> > 
> > Full details at
> > http://developer.osdl.org/cliffw/reaim/index.html
> > code at 
> > bk://developer.osdl.org/osdl-aim-7
> > 
> 
> OK, I can reproduce this on 4way.
> 
> Binary searching (insert gratuitous rant about benchmarks that take more
> than two minutes to complete) reveals that the slowdown is due to
> sched-2.6.0-test2-mm2-A3.

[Rant response]
For a short test run, you can run a small number of iterations like this:
./reaim -s2 -e10 -i2 -f./workfile.new_dbase

( 2->10 users, increment by 2)

That takes about 5 minutes on our 4-way.

Or, run one iteration with a large user count:

./reaim -s25 -e25 -f ./workifile.foo

cliffw


> 
> So mm4 with everthing up to but not including sched-2.6.0-test2-mm2-A3:
> 
> 	Max Jobs per Minute 1467.06
> 	Max Jobs per Minute 1478.82
> 	Max Jobs per Minute 1473.36
> 
> 	3853.55s user 264.31s system 370% cpu 18:31.95 total
> 
> After adding sched-2.6.0-test2-mm2-A3:
> 
>         Max Jobs per Minute 1375.63
>         Max Jobs per Minute 1278.40
>         Max Jobs per Minute 1293.11
> 
>         4416.70s user 275.61s system 374% cpu 20:53.58 total
> 
> A 10% regression there, mainly user time.
> 
> 
> The test is:
> 
> - build bk://developer.osdl.org/osdl-aim-7
> 
> - cd src
> 
> - time ./reaim -s4 -q -t -i4 -f./workfile.new_dbase -r3 -b -l./reaim.config
> 
> 
> 



  reply	other threads:[~2003-08-06 19:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 16:07 Cliff White
2003-08-06  5:23 ` Andrew Morton
2003-08-06 19:10   ` Cliff White [this message]
2003-08-07  2:40     ` Con Kolivas
2003-08-07  5:11       ` Nick Piggin
2003-08-07  5:41         ` Con Kolivas
2003-08-07  8:25           ` Nick Piggin
2003-08-07 10:01             ` Con Kolivas
2003-08-07 10:05               ` Nick Piggin
2003-08-08 20:58       ` Cliff White

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=200308061910.h76JAYw16323@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®