public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Nick Piggin <piggin@cyberone.com.au>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: ricklind@us.ibm.com
Subject: Re: Nick's scheduler v16
Date: Tue, 21 Oct 2003 14:16:08 -0700	[thread overview]
Message-ID: <56890000.1066770968@flay> (raw)
In-Reply-To: <3F913704.5040707@cyberone.com.au>

> 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.

Interesting ... some things get getter, some worse:

Kernbench: (make -j N vmlinux, where N = 2 x num_cpus)
                              Elapsed      System        User         CPU
              2.6.0-test8       45.20      100.97      566.65     1476.25
         2.6.0-test8-nick       44.81       93.98      568.49     1477.50
        2.6.0-test8-nick2       44.78       94.69      568.81     1482.00

elapsed is a tiny bit faster, system is significantly less, but with
higher parallelism:


Kernbench: (make -j vmlinux, maximal tasks)
                              Elapsed      System        User         CPU
              2.6.0-test8       45.86      119.41      569.66     1502.00
         2.6.0-test8-nick       47.00      112.75      590.40     1495.00
        2.6.0-test8-nick2       47.11      112.86      590.31     1491.50

elapsed is definitely worse now.
SDET is a happy bunny though:

SDET 128  (see disclaimer)
                           Throughput    Std. Dev
              2.6.0-test8       100.0%         0.3%
         2.6.0-test8-nick       109.9%         0.2%

Much of the changes there might just be backing out Con's interactivity
changes ...

M.


  parent reply	other threads:[~2003-10-21 21:16 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 [this message]
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
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=56890000.1066770968@flay \
    --to=mbligh@aracnet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    --cc=ricklind@us.ibm.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