mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm3 osdl-aim-7 regression
Date: Fri, 08 Aug 2003 13:58:31 -0700	[thread overview]
Message-ID: <200308082058.h78KwV300335@mail.osdl.org> (raw)
In-Reply-To: Message from Con Kolivas <kernel@kolivas.org>  of "Thu, 07 Aug 2003 12:40:54 +1000." <200308071240.54863.kernel@kolivas.org>

> On Thu, 7 Aug 2003 05:10, Cliff White wrote:
> > > 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.
> 
> This is most likely the round robinning of tasks every 25ms. The extra 
> overhead of nanosecond timing I doubt could make that size difference (but I 
> could be wrong). There is some tweaking of this round robinning in my code 
> which may help this, but it won't bring it back up to original performance I 
> believe. Two things to try are add my patches up to O12.3int first to see how 
> much (if at all!) it helps, and change TIMESLICE_GRANULARITY in sched.c to 
> (MAX_TIMESLICE) which basically disables it completely. If there is still  a 
> drop in performance with this, the remainder is the extra locking/overhead in 
> nanosecond timing.
> 
> Con
> 
Added your patches to PLM, from your web site. We've had other issues slowing 
up the
4-cpu queue, but the two CPU tests ran. On these smaller platforms, not seeing 
big
difference between the patches.

STP id PLM# Kernel Name         Workfile   MaxJPM  MaxUser Host     %Change
 277231 2042 CK-O13-O13.1int-1  new_dbase  1333.60  22     stp2-002 0.00
 277230 2041 CK-O12.3-O13int-1  new_dbase  1344.23  24     stp2-003 0.80
 277228 2040 CK-012.2-O12.3int-1 new_dbase 1328.86  22     stp2-002 -0.36
All are a bit better than stock:
276572 2020 linux-2.6.0-test2    new_dbase  1320.68 22	   stp2-000 -0.96
---- 
Code location:
bk://developer.osdl.org/osdl-aim-7
More results:
http://developer.osdl.org/cliffw/reaim/index.html

Run parameters: 

./reaim -s2 -x -t -i2 -f workfile.new_dbase -r3 -b -l./stp.config

cliffw



      parent reply	other threads:[~2003-08-08 20:58 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
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 [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=200308082058.h78KwV300335@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®