All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Nick's scheduler v16 - reaim
Date: Thu, 23 Oct 2003 12:02:54 +1000	[thread overview]
Message-ID: <3F9736CE.8050007@cyberone.com.au> (raw)
In-Reply-To: <200310221407.h9ME7mM14401@mail.osdl.org>



Cliff White wrote:

>>
>>
>>>>I'm starting to do some large SMP / NUMA testing. Fixed and changed quite
>>>>a bit. It isn't too bad, although I'm only testing dbench, tbench, and
>>>>volanomark at the moment.
>>>>
>>>>These SMP and NUMA changes are not tied to my interactivity stuff, so its
>>>>possible they could get included if they turn out well. If you find any
>>>>problems with it (high end or interactivity), please let me know.
>>>>
>>>>
>
>Results from reaim aren't encouraging.
>patch was applied against 2.6.0-test8 - the result
>is PLM #2232
>
>STP id  kernal name       Max JPM   Max User Pct    elevator
>281932	nick_v16          4923.08    60	     0.00   AS
>281933	nick_v16          5196.06    68	     5.54   deadline
>281722	linux-2.6.0-test8 5432.77    92	     9.38   deadline
>281792	2.6.0-test8-mm1   5384.41    92	     8.56   deadline
>281790	2.6.0-test8-mm1   5392.65    88      8.7    AS
>
>The kernel doesn't perform well at larger user numbers.
>Notice the different in max users.
>Compare the graphs for jobs per minute, the usual graph
>is quite flat, see:
>http://khack.osdl.org/stp/281932/results/jpm.png
>
>With the v16 scheduler, jobs per minute falls off rapidly
>as user number increases giving graph with a steep slope, 
>not good.
>http://khack.osdl.org/stp/281790/results/jpm.png
>Further results: http://www.developer.osdl.org/reaim/index.html
>

Hi Cliff,

Yeah, unfortunately this graph has been a feature of my scheduler for
quite a while :( I think it is caused either by too much balancing
or timeslices getting too small because there are a lot of threads
blocking. Anyway, if you had the time to test this one would be really
good.

http://www.kerneltrap.org/~npiggin/v16/sched-rollup-nopolicy-v16.gz

Nick


  reply	other threads:[~2003-10-23  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18 12:50 Nick's scheduler v16 Nick Piggin
2003-10-18 13:18 ` Nick Piggin
2003-10-21 21:16 ` Martin J. Bligh
2003-10-22  1:43   ` Nick Piggin
2003-10-22 14:07     ` Nick's scheduler v16 - reaim Cliff White
2003-10-23  2:02       ` Nick Piggin [this message]
2003-10-30  3:41 ` Nick's scheduler v17a Nick Piggin
2003-10-31 22:57   ` Rhino
2003-11-03  4:47     ` Nick Piggin

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=3F9736CE.8050007@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=cliffw@osdl.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 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.