public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Con Kolivas <kernel@kolivas.org>, Nick Piggin <piggin@cyberone.com.au>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Performance of -mm2 and -mm4
Date: Wed, 25 Aug 2004 15:29:38 -0700	[thread overview]
Message-ID: <7230000.1093472977@[10.10.2.4]> (raw)
In-Reply-To: <cone.1093310997.326407.10766.502@pc.kolivas.org>

>>>> The -mm4 looks more like sched stuff to me (copy_to/from_user, etc),
>>>> but the -mm2 stuff looks like something else. Buggered if I know what.
>>>> -mm3 didn't compile cleanly, so I didn't bother, but I prob can if you
>>>> like.
>>>> 
>>> 
>>> If you suspect the scheduler, you could try bumping SD_NODES_PER_DOMAIN in 
>>> kernel/sched.c to a larger value (e.g. the number of nodes in your system).  
>>> That'll make the scheduler balance more aggressively across the whole system.
>>> 
>>> 
>> 
>> Try increasing /proc/sys/kernel/base_timeslice as well.
> 
> Or back out nicksched.patch

Yeah, that mostly fixed it.

Kernbench: (make -j N vmlinux, where N = 16 x num_cpus)
                              Elapsed      System        User         CPU
                  2.6.8.1       44.82       97.19      574.55     1497.33
              2.6.8.1-mm4       46.82      107.47      594.15     1497.33
           2.6.8.1-mm4-nn       44.93       96.33      576.44     1496.33

Kernbench: (make -j vmlinux, maximal tasks)
                              Elapsed      System        User         CPU
                  2.6.8.1       43.90       87.76      572.94     1505.67
              2.6.8.1-mm4       45.87       97.60      595.23     1510.00
           2.6.8.1-mm4-nn       44.53       90.71      575.68     1495.67


  reply	other threads:[~2004-08-25 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23 16:58 Performance of -mm2 and -mm4 Martin J. Bligh
2004-08-23 21:31 ` Jesse Barnes
2004-08-24  0:41   ` Nick Piggin
2004-08-24  1:29     ` Con Kolivas
2004-08-25 22:29       ` Martin J. Bligh [this message]
2004-08-24  3:23 ` Nick Piggin
2004-08-24  3:26   ` Martin J. Bligh

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='7230000.1093472977@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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