From: Nick Piggin <piggin@cyberone.com.au>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UP Regression (was) Re: Scaling noise
Date: Thu, 04 Sep 2003 10:54:26 +1000 [thread overview]
Message-ID: <3F568D42.1070004@cyberone.com.au> (raw)
In-Reply-To: <200309031551.h83Fpu413835@mail.osdl.org>
Cliff White wrote:
>[snip]
>.
>
>>I don't think anyone advocates sacrificing UP performance for 32 ways, but
>>as he says it can happen .1% at a time.
>>
>>But it looks like 2.6 will scale well to 16 way and higher. I wonder if
>>there are many regressions from 2.4 or 2.2 on small systems.
>>
>>
>>
>On the Scalable Test Platform, running osdl-aim-7, for the
>UP case, 2.4 is a bit better than 2.6, this is consistent across
>many runs. For SMP, 2.6 is better, but the delta is rather
>small, until we get to 8 CPUS. We have a lot of un-parsed data from other
>tests - might be some trends there also.
>See http://developer.osdl.org/cliffw/reaim/index.html
>2.4 kernels are at the bottom of the page.
>
Forgive my ignorance of your benchmarks, but this might very well
be HZ == 1000?
prev parent reply other threads:[~2003-09-04 0:54 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 4:03 Scaling noise Larry McVoy
2003-09-03 4:12 ` Roland Dreier
2003-09-03 4:20 ` Larry McVoy
2003-09-03 15:12 ` Martin J. Bligh
2003-09-03 4:18 ` Anton Blanchard
2003-09-03 4:29 ` Larry McVoy
2003-09-03 4:33 ` CaT
2003-09-03 5:08 ` Larry McVoy
2003-09-03 5:44 ` Mikael Abrahamsson
2003-09-03 6:12 ` Bernd Eckenfels
2003-09-03 12:09 ` Alan Cox
2003-09-03 15:10 ` Martin J. Bligh
2003-09-03 16:01 ` Jörn Engel
2003-09-03 16:21 ` Martin J. Bligh
2003-09-03 19:41 ` Mike Fedyk
2003-09-03 20:11 ` Martin J. Bligh
2003-09-04 20:36 ` Rik van Riel
2003-09-04 20:47 ` Martin J. Bligh
2003-09-04 21:30 ` William Lee Irwin III
2003-09-03 8:11 ` Giuliano Pochini
2003-09-03 14:25 ` Steven Cole
2003-09-03 12:47 ` Antonio Vargas
2003-09-03 15:31 ` Steven Cole
2003-09-04 1:50 ` Daniel Phillips
2003-09-04 1:52 ` Larry McVoy
2003-09-04 4:42 ` David S. Miller
2003-09-08 19:40 ` bill davidsen
2003-09-04 2:18 ` William Lee Irwin III
2003-09-04 2:19 ` Steven Cole
2003-09-04 2:35 ` William Lee Irwin III
2003-09-04 2:40 ` Steven Cole
2003-09-04 3:20 ` Nick Piggin
2003-09-04 3:07 ` Daniel Phillips
2003-09-08 19:27 ` bill davidsen
2003-09-08 19:12 ` bill davidsen
2003-09-03 16:37 ` Kurt Wall
2003-09-06 15:08 ` Pavel Machek
2003-09-08 13:38 ` Alan Cox
2003-09-09 6:11 ` Rob Landley
2003-09-09 16:07 ` Ricardo Bugalho
2003-09-10 5:14 ` Rob Landley
2003-09-10 5:45 ` David Mosberger
2003-09-10 10:10 ` Ricardo Bugalho
2003-09-03 6:28 ` Anton Blanchard
2003-09-03 6:55 ` Nick Piggin
2003-09-03 15:23 ` Martin J. Bligh
2003-09-03 15:39 ` Larry McVoy
2003-09-03 15:50 ` Martin J. Bligh
2003-09-04 0:49 ` Larry McVoy
2003-09-04 2:21 ` Daniel Phillips
2003-09-04 2:35 ` Martin J. Bligh
2003-09-04 2:46 ` Larry McVoy
2003-09-04 4:58 ` David S. Miller
2003-09-10 15:47 ` Lock EVERYTHING (for testing) [was: Re: Scaling noise] Timothy Miller
2003-09-04 4:49 ` Scaling noise David S. Miller
2003-09-08 19:50 ` bill davidsen
2003-09-08 23:39 ` Peter Chubb
2003-09-03 17:16 ` William Lee Irwin III
2003-09-03 15:51 ` UP Regression (was) " Cliff White
2003-09-03 17:21 ` William Lee Irwin III
2003-09-03 18:53 ` Cliff White
2003-09-04 0:54 ` Nick Piggin [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=3F568D42.1070004@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.