mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Klinkert <simon.klinkert@gmail.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, Trond.Myklebust@netapp.com
Subject: Re: Meaningless load?
Date: Thu, 11 Oct 2012 15:17:59 +0200	[thread overview]
Message-ID: <C1DCAB1C-D69C-411C-9CE7-07EC097DF93E@gmail.com> (raw)
In-Reply-To: <1349943207.6989.77.camel@marge.simpson.net>


On 11.10.2012, at 10:13, Mike Galbraith wrote:

>> On 11.10.2012, at 06:02, Mike Galbraith wrote:
>> 
>>> Makes perfect sense to me. Work _is_ stack this high. We don't and
>>> can't know whether the mountain is made of popcorn balls or
>> boulders.
>> 
>> That's the point. Afaik the D state never represents 'work'. These
>> processes are waiting for something.
> 
> Yeah, the whole pile is waiting, but they're not idle.  There are N
> tasks pointed at CPUs.
>> 
>> Let's say we have 10,000 processes in the D state (and thus a load of
>> ~10,000) doing nothing. What should the load tell me? The machine is
>> under fire? There is nothing to do? There might be something to do but
>> the machine doesn't know?
> 
> They are doing something, just not at the particular instant you see
> them in D state.  D state pushing load through the roof tells you that
> you have a bottleneck.  Whether the bottleneck is a bit of spinning rust
> or insufficient NR_CPUS doesn't matter much, both are bottlenecks.

Your explanation sounds correct to me but I think in my case, there are only 2-3 process 
waiting for spinning rust (or rather nfs) and the other processes are all in a heavy lock 
contention in the VFS layer. So a load of 10,000 is helpful to indicate that there is a (software)
bottleneck but if I want to see the 'real (work)load' on this machine it isn't really helpful to show 
a load of 10,000 instead of three or whatever. It's a question of interpretation.

Simon



      reply	other threads:[~2012-10-11 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 15:44 Simon Klinkert
2012-10-10 16:22 ` Peter Zijlstra
2012-10-11  7:19   ` Simon Klinkert
2012-10-11  8:13     ` Mike Galbraith
2012-10-11 13:17       ` Simon Klinkert [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=C1DCAB1C-D69C-411C-9CE7-07EC097DF93E@gmail.com \
    --to=simon.klinkert@gmail.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®