mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: drago01 <drago01@gmail.com>
To: kernel list <linux-kernel@vger.kernel.org>
Cc: mingo@redhat.com, Chuck Ebbert <cebbert@redhat.com>
Subject: Re: sched regression introduced by NO_NEW_FAIR_SLEEPERS
Date: Sun, 27 Sep 2009 21:52:05 +0200	[thread overview]
Message-ID: <f6ca9fed0909271252m395a6det40fede669495c994@mail.gmail.com> (raw)
In-Reply-To: <f6ca9fed0909271250h61e2ce94n31c9f23e835f802c@mail.gmail.com>

On Sun, Sep 27, 2009 at 9:50 PM, 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".

Well ok I can expirence some delays when switching workspaces with 100
tasks but it is still better than 8 with "NO_NEW_FAIR_SLEEPERS"

  reply	other threads:[~2009-09-27 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 19:47 drago01
2009-09-27 19:50 ` drago01
2009-09-27 19:52   ` drago01 [this message]
2009-10-03 10:47   ` Ingo Molnar
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=f6ca9fed0909271252m395a6det40fede669495c994@mail.gmail.com \
    --to=drago01@gmail.com \
    --cc=cebbert@redhat.com \
    --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

all inboxes | Powered by JetHome®