mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alberto Gonzalez <info@gnebu.es>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about fair schedulers
Date: Wed, 27 Jun 2007 14:39:20 +0200	[thread overview]
Message-ID: <200706271439.21043.info@gnebu.es> (raw)
In-Reply-To: <B6065113-E9C7-42CE-A43D-55E6BF1EE2C0@mac.com>

On Saturday 23 June 2007, Kyle Moffett wrote:
> On Jun 22, 2007, at 18:07:15, Alberto Gonzalez wrote:
> > P.S: As a second thought, a fair scheduler could behave really good
> > in other scenarios, like a server running a busy forum on apache
> > +mysql+php. Besides, this is a more real world scenario (and easier
> > to benchmark). Why aren't people testing these schedulers under
> > this kind of load?
>
> That kind of load is boring precisely because it doesn't care about
> interactivity.  CFS/SD aren't a whole lot different from mainline-
> without-interactivity in that respect, precisely because the latency
> of the network is between ten and a hundred times more than the
> latency of the scheduler.  The only time it really matters is with
> desktops where users care about smoothness.

Well, I've just seen some benchmarks of this kind with CFS and it does make a 
difference. The scalability problem with MySQL seems to get solved with this 
scheduler. However, the peak throughput is quite lower than with the same 
kernel/glibc version and mainline scheduler.

http://jeffr-tech.livejournal.com/

Anyway, this kind of testing seems to be useful. Linux is too widely deployed 
in servers to ignore the behavior of a CPU scheduler in that scenario.

Cheers,
Alberto.

  parent reply	other threads:[~2007-06-27 12:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 22:07 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 [this message]
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
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=200706271439.21043.info@gnebu.es \
    --to=info@gnebu.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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®