public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Chris Friesen <cfriesen@nortel.com>
Cc: "Nico Schümann" <spam@nico22.de>, linux-kernel@vger.kernel.org
Subject: Re: CFS not suitable for desktop computers
Date: Tue, 05 May 2009 07:42:08 +0200	[thread overview]
Message-ID: <1241502128.5505.62.camel@marge.simson.net> (raw)
In-Reply-To: <49FF57AC.7070104@nortel.com>

On Mon, 2009-05-04 at 15:01 -0600, Chris Friesen wrote:
> Nico Schümann wrote:
> > Thank you Ray Lee and Mike Galbraith for your responses, I ran the 
> > script and attached its gathered information.
> > 
> > Mike Galbraith wrote:
> >> How hard is hard?  Can you describe the loads you're having trouble
> >> with, and the hardware you're running them on?
> >>
> >>   
> > I could reproduce "hard" load by just compiling the linux kernel, make 
> > -j3 while reading mails with Thunderbird, which is not that hard 
> > foreground load. Thunderbird starts reacting really slowly while compiling.
> 
> I wonder if this could be related to I/O rather than the task scheduler 
> proper.

That's something I was wondering as well, particularly when I noticed
he's using data=journal and anticipatory io-scheduler.

Doing some testing with different journal modes and io-schedulers
recently, I found loads where anticipatory didn't do very well compared
to cfq, and journal mode can make a tremendous difference ala..

time ./postmark < config

          ordered     writeback      guarded      journal
real    11m18.752s    3m5.160s     3m1.367s    15m18.610s
user    0m5.672s      0m6.220s     0m5.976s    0m6.856s
sys     0m26.094s     0m20.965s    0m21.673s   0m20.969s

real    9m33.922s     2m53.984s    3m6.284s    15m12.969s
user    0m5.700s      0m5.976s     0m6.356s    0m6.980s
sys     0m26.682s     0m21.413s    0m20.717s   0m19.641s

real    10m8.766s     3m0.382s     2m58.714s   15m33.400s
user    0m5.608s      0m6.080s     0m6.232s    0m6.776s
sys     0m27.130s     0m21.041s    0m21.709s   0m19.489s

	-Mike


  reply	other threads:[~2009-05-05  5:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 19:26 CFS not suitable for desktop computers Nico Schümann
2009-05-03 23:24 ` Ray Lee
     [not found] ` <1241424835.26855.102.camel@marge.simson.net>
2009-05-04 15:16   ` Nico Schümann
2009-05-04 17:59     ` Mike Galbraith
2009-05-04 21:01     ` Chris Friesen
2009-05-05  5:42       ` Mike Galbraith [this message]
2009-05-05  7:51         ` Mike Galbraith
2009-05-06  8:03     ` Peter Zijlstra

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=1241502128.5505.62.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spam@nico22.de \
    /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