The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: drago01 <drago01@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mike Galbraith <efault@gmx.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	mingo@redhat.com, Chuck Ebbert <cebbert@redhat.com>
Subject: Re: sched regression introduced by NO_NEW_FAIR_SLEEPERS
Date: Sat, 3 Oct 2009 12:47:23 +0200	[thread overview]
Message-ID: <20091003104723.GC15919@elte.hu> (raw)
In-Reply-To: <f6ca9fed0909271250h61e2ce94n31c9f23e835f802c@mail.gmail.com>


* drago01 <drago01@gmail.com> wrote:

> On Sun, Sep 27, 2009 at 9:47 PM, drago01 <drago01@gmail.com> wrote:
> > Hi,
> >
> > Chuck has backported some scheduler patches from 2.6.32 to the fedora kernel.
> >
> > I did the following test to test the new scheduler (cpu is a core i7
> > 920 4 cores + HT).
> >
> > run 8 "md5sum /dev/urandom" task and try to use the desktop (compiz).
> >
> > The result was that moving windows or rotating the cube is very slow.
> > (same happens with pure metacity but is is worse in compiz).
> >
> > Mounting debugfs and doing "echo NEW_FAIR_SLEEPERS > sched_features"
> > results into a useable desktop while the 8 md5sum tasks are running
> > (ie. the system behaves as if they where not running at all from an
> > interactivity pov).
> >
> >
> > P.S: please CC me when replying.
> >
> 
> With "NEW_FAIR_SLEEPERS" I can even run 100(!)  "md5sum" task without 
> any effect on interactivity. (still have not found a number of tasks 
> needed to make the system unresponsive as with 8 with 
> "NO_NEW_FAIR_SLEEPERS".

Can you try the latest -tip tree please:

  http://people.redhat.com/mingo/tip.git/README

There we default to FAIR_SLEEPERS + GENTLE_FAIR_SLEEPERS - which should 
give much of the new-fair-sleepers advantage.

There's also a new tool, 'perf sched', which you can install via:

  cd tools/perf/
  make -j install

And use like this to measure latencies in the system:

 $ perf sched record sleep 1
 [ perf record: Woken up 1 times to write data ]
 [ perf record: Captured and wrote 0.059 MB perf.data (~2563 samples) ]

 $ perf sched latency

 -----------------------------------------------------------------------------------------
  Task                  |   Runtime ms  | Switches | Average delay ms | Maximum delay ms |
 -----------------------------------------------------------------------------------------
  events/12:47          |      0.007 ms |        1 | avg:    0.054 ms | max:    0.054 ms |
  events/2:37           |      0.128 ms |        1 | avg:    0.016 ms | max:    0.016 ms |
  at-spi-registry:3292  |      0.752 ms |       20 | avg:    0.015 ms | max:    0.023 ms |
  Xorg:3161             |      0.519 ms |       20 | avg:    0.015 ms | max:    0.024 ms |
  perf:19070            |     21.241 ms |        5 | avg:    0.012 ms | max:    0.019 ms |
  events/1:36           |      0.009 ms |        1 | avg:    0.009 ms | max:    0.009 ms |
  hald-addon-stor:2790  |      0.204 ms |        9 | avg:    0.009 ms | max:    0.011 ms |
  scsi_eh_5:1072        |      0.200 ms |       12 | avg:    0.009 ms | max:    0.009 ms |
  events/0:35           |      0.007 ms |        1 | avg:    0.008 ms | max:    0.008 ms |
  ksoftirqd/12:28       |      0.088 ms |        5 | avg:    0.005 ms | max:    0.009 ms |
  sleep:19071           |      0.668 ms |        3 | avg:    0.005 ms | max:    0.008 ms |
  migration/13:29       |      0.000 ms |        1 | avg:    0.003 ms | max:    0.003 ms |
 -----------------------------------------------------------------------------------------
  TOTAL:                |     23.824 ms |       79 |
 ---------------------------------------------------

Thanks,

	Ingo

  parent reply	other threads:[~2009-10-03 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 19:47 sched regression introduced by NO_NEW_FAIR_SLEEPERS drago01
2009-09-27 19:50 ` drago01
2009-09-27 19:52   ` drago01
2009-10-03 10:47   ` Ingo Molnar [this message]
2009-10-03 13:23     ` drago01
2009-10-03 14:49       ` Ingo Molnar
2009-09-27 20:06 ` drago01

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=20091003104723.GC15919@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cebbert@redhat.com \
    --cc=drago01@gmail.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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