From: Ingo Molnar <mingo@elte.hu>
To: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Turner <pjt@google.com>, Venki Pallipadi <venki@google.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] sched: fix nohz idle load balancer issues
Date: Tue, 27 Sep 2011 15:39:09 +0200 [thread overview]
Message-ID: <20110927133909.GB26578@elte.hu> (raw)
In-Reply-To: <20110927103106.GD4357@linux.vnet.ibm.com>
* Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> * Ingo Molnar <mingo@elte.hu> [2011-09-27 08:32:24]:
>
> > What are the tasks doing which are running - are they plain burning
> > CPU time? If the tasks do something more complex, do you also have a
> > measure of how much work gets done by the workload, per second?
>
> They are simple cpu hogs at this time.
>
> > Percentual changes in that metric would be nice to include in an
> > additional column - that way we can see that it's not only idle
> > that has gone down, but workload performance has gone up too.
>
> Ok, good point.
>
> > In fact even if there was only a CPU burning loop in the workload it
> > would be nice to make that somewhat more sophisticated by letting it
> > process some larger array that has a cache footprint. This mimics
> > real workloads that don't just spin burning CPU time but do real data
> > processing.
> >
> > For any non-trivial workload it's possible to reduce idle time
> > without much increase in work done and in fact it's possible to
> > decrease idle time *and* work done - so we need to see more clearly
> > here and make sure it's all an improvement.
>
> Ok - I will run a cpu intensive benchmark and get some numbers on
> how benchmark score varies with the patch applied. I can pick a
> simple matrix multiplication type benchmark, unless you have other
> suggestions!
Yeah, matrix multiplication would be fine i think.
You could create it yourself and add it into
tools/perf/bench/cpu-matrix.c as a new 'perf bench cpu matrix'
testcase - perhaps with a '-s 10m' parameter that defines the size of
the matrices, and a '-i 1000' parameter to specify the number of
iterations - or so.
We could use that for scheduler HPC benchmarking in the future as
well.
Thanks,
Ingo
next prev parent reply other threads:[~2011-09-27 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:50 Srivatsa Vaddagiri
2011-09-26 12:01 ` Srivatsa Vaddagiri
2011-09-27 6:32 ` Ingo Molnar
2011-09-27 10:31 ` Srivatsa Vaddagiri
2011-09-27 13:39 ` Ingo Molnar [this message]
2011-09-27 19:53 ` Venki Pallipadi
2011-09-27 23:49 ` Suresh Siddha
2011-09-28 4:15 ` Srivatsa Vaddagiri
2011-09-29 0:47 ` Suresh Siddha
2011-09-29 2:13 ` Srivatsa Vaddagiri
2011-09-29 8:15 ` Peter Zijlstra
2011-09-29 17:13 ` Suresh Siddha
2011-09-28 4:34 ` Srivatsa Vaddagiri
2011-09-28 4:39 ` Srivatsa Vaddagiri
2011-09-28 5:06 ` Srivatsa Vaddagiri
2011-09-28 14:17 ` Srivatsa Vaddagiri
2011-09-28 14:27 ` Srivatsa Vaddagiri
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=20110927133909.GB26578@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pjt@google.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=venki@google.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
all inboxes | Powered by JetHome®