From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: Tom Spink <tspink@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about fair schedulers
Date: Wed, 27 Jun 2007 16:28:21 -0400 [thread overview]
Message-ID: <4682C865.7080307@tmr.com> (raw)
In-Reply-To: <200706231326.34918.info@gnebu.es>
Alberto Gonzalez wrote:
> On Saturday 23 June 2007, Tom Spink wrote:
>> Alberto,
>>
>> If you're feeling adventurous, grab the latest kernel and patch it
>> with Ingo's scheduler: CFS.
>>
>> You may be pleasantly surprised.
>
> Thanks, I might if I have to courage to patch and compile my own kernel :)
>
> However, I'd also need to change all my applications to set them with the
> right priority to see the good results, so I think I might just wait until it
> lands in mainline.
In general not the case. I generally don't diddle my priorities, there's
rarely a need.
>
> Just to check if I understood everything correctly:
>
> The mainline scheduler tries to be smart and guess the priority of each task,
> and while it mostly hits the nail right in the head, sometimes it hits you
> right in the thumb.
>
> Fair schedulers, on the contrary, forget about trying to be smart and just
> care about being fair, leaving the priority settings to where they belong:
> applications.
>
> Is this more or less correct?
Incomplete. The CFS scheduler seems to do better with latency, so you
may get less CPU to a process but it doesn't wind up waiting a long time
to get a fair share. So it "feels better" without micro tuning.
Face it, if you have more jobs than CPU no scheduler is going to make
you really happy.
>
> Alberto.
>
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-06-27 20:27 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
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 [this message]
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=4682C865.7080307@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tspink@gmail.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 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.