From: Alberto Gonzalez <info@gnebu.es>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about fair schedulers
Date: Sat, 23 Jun 2007 10:01:02 +0200 [thread overview]
Message-ID: <200706231001.02497.info@gnebu.es> (raw)
In-Reply-To: <20070623090655.36d1794c@localhost>
Thanks for your thoughts.
On Saturday 23 June 2007, Paolo Ornati wrote:
> On Sat, 23 Jun 2007 00:07:15 +0200
>
> Alberto Gonzalez wrote:
> > My conclusion is that SD behaves as expected: it's more fair. But for a
> > desktop, shouldn't an "intelligently unfair" scheduler be better?
>
> "intelligently unfair" is what the current scheduler is (because of
> interactivity estimator).
>
> When it works (say 90% of the time) the desktop feels really good...
> but when it doesn't it can be a disaster.
I see. So you mean that in 90% of the cases the mainline scheduler behaves
better than fair schedulers, but when its "logic" fails it behaves much worse
(the other 10% cases)? In my very simple test scenario the mainline scheduler
did behave much better. Maybe the problem comes with very complex scenarios
like the ones I've seen when testing these 2 fair schedulers (something like
compiling a kernel while you open 5 instances of glxgears, write an email,
play music in Amarok and watch 2 HD videos all at the same time). The
question would then be if these kind of situations are likely to happen in
real world, or even if it doesn't make more sense to try to improve the logic
of the mainline scheduler so that those 10% cases are handled better instead
of writing a new one that would behave worse in 90% of the cases and better
in the other 10%.
Alberto.
next prev parent reply other threads:[~2007-06-23 8:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 22:07 Question about fair schedulers Alberto Gonzalez
2007-06-23 0:55 ` Kyle Moffett
2007-06-23 7:46 ` Alberto Gonzalez
2007-06-23 16:35 ` Kyle Moffett
2007-06-23 17:28 ` Alberto Gonzalez
2007-06-24 20:57 ` Jesper Juhl
2007-06-24 19:36 ` David Schwartz
2007-06-26 12:19 ` Helge Hafting
2007-06-27 12:39 ` Alberto Gonzalez
2007-06-23 7:06 ` Paolo Ornati
2007-06-23 8:01 ` Alberto Gonzalez [this message]
2007-06-23 8:23 ` Willy Tarreau
2007-06-23 9:18 ` Alberto Gonzalez
2007-06-23 9:28 ` Russell Harmon
2007-06-23 10:30 ` Willy Tarreau
2007-06-23 10:45 ` Alberto Gonzalez
2007-06-23 10:50 ` Willy Tarreau
2007-06-23 11:00 ` Alberto Gonzalez
2007-06-23 11:05 ` Tom Spink
2007-06-23 11:26 ` Alberto Gonzalez
2007-06-23 11:51 ` Willy Tarreau
2007-06-27 20:28 ` Bill Davidsen
2007-06-23 13:26 ` Paolo Ornati
2007-06-23 13:56 ` Alberto Gonzalez
2007-06-23 14:28 ` Paolo Ornati
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=200706231001.02497.info@gnebu.es \
--to=info@gnebu.es \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.