public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: l.genoni@oltrelinux.com
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
	Rajib Majumder <rajibm2005@gmail.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	l.genoni@sns.it
Subject: Re: Kernel Scalability
Date: Wed, 2 May 2007 11:06:45 -0700	[thread overview]
Message-ID: <20070502180645.GY19966@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021933320.14034@Phoenix.oltrelinux.com>

On Wed, 2 May 2007, Daniel J Blueman wrote:
>> There are 128-processor IA64 systems which run recent 2.6 kernels out
>> there; the per-processor counters, RCU and page-fault scalability work
>> has been instrumental to the necessary scaling for decent resource
>> usage on these.
>> IIRC, there were some patches being developed to improve pagecache
>> scalability lately too, but I guess it all depends on what kind of
>> workload you have...

On Wed, May 02, 2007 at 07:39:48PM +0200, l.genoni@oltrelinux.com wrote:
> To stay on systems probably more familiar to the user who asked this 
> question, there are also some 64 core X86_64 bot AMD and Intel out there, 
> here the 2.6 kernel is doing 
> very well even on those intel CPU with shared L2 cache.
> I have some 16 and 32 core Opteron and never had scalability problems.
> You have to pay a lot of attention to your kernel configuration  (100 HZ, 
> just BKL preemption), and to the 
> filesystems you decide to use.

One doesn't typically experience scalability problems per se. One
rather compares slopes of scaling lines and notes relative scaling
across kernels, be they versions of the same kernel or different
codebases altogether. It's still possible to have scalability
problems, of course, where things basically slowdown severely or
appear to stop entirely.

Nonlinear scalability is generally considered to be where the limits
of scaling set in. There is usually linear scaling until some number
of processors, and then the limit is where the linearity breaks down.
Linear scalability is defined as adding resources (e.g. cpus) to the
system resulting in a linear increase in performance.

To characterize a kernel's scalability, one should say three things:
(1) workload/benchmark
(2) linear scaling coefficient
(3) upper limit on linearity

So you would say that when running dbench, Linux scales with a
coefficient of 0.85 up to 78 processors or similar.


-- wli

  reply	other threads:[~2007-05-02 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 15:43 Kernel Scalability Daniel J Blueman
2007-05-02 16:54 ` Tony Luck
2007-05-02 17:39 ` l.genoni
2007-05-02 18:06   ` William Lee Irwin III [this message]
2007-05-04 16:45   ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2007-05-02 12:56 Rajib Majumder
2007-05-02 16:54 ` Kevin Fox
2007-05-04 16:43   ` Christoph Lameter
2007-05-02 17:55 ` Eric W. Biederman

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=20070502180645.GY19966@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=daniel.blueman@gmail.com \
    --cc=l.genoni@oltrelinux.com \
    --cc=l.genoni@sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajibm2005@gmail.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