All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org (Markus   Törnqvist)
To: linux-kernel@vger.kernel.org
Subject: Re: Scheduler experiences
Date: Sun, 5 Sep 2004 17:25:02 +0300	[thread overview]
Message-ID: <20040905142502.GQ26192@nysv.org> (raw)
In-Reply-To: <1094386464.18114.0.camel@localhost>

Kasper Sandberg wrote:

>Hey, i wonder which scheduler you people have the best experiences with,
>staircase or nicksched?

I've been a fan of Staircase's for a long time; it simply responded faster
and launched progs faster.

I haven't tried nicksched in a while, but it didn't perform as well as
Staircase.

Having a batched mprime torture test in the background still allows me to
play a movie in mplayer, compile a kernel, listen to a CD and browse
the web without glitches. Not that I'd normally watch a movie and listen to
a CD at the same time ;)

Going to try Nicksched again RSN to see if it handles the same load, but
still I have to say I'm mighty pleased with Staircase and the rest of
Con's patches.

(Running 2.6.8.1-cko3 with the lenient patch of -ck6 at the moment)
(This is in an Athlon 1.3GHz with 512MB of RAM and roughly the same of swap)

-- 
mjt


  parent reply	other threads:[~2004-09-05 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 12:14 Scheduler experiences Kasper Sandberg
2004-09-05 12:25 ` DaMouse
2004-09-05 12:37   ` Nick Piggin
2004-09-05 12:43     ` DaMouse
2004-09-05 12:56       ` Nick Piggin
2004-09-05 12:49 ` Piotr Neuman
2004-09-05 14:25 ` Markus   Törnqvist [this message]
2004-09-05 15:55   ` Scheduler experiences (with Reiser4 bug report) mjt
2004-09-05 15:55     ` Markus   Törnqvist
2004-09-05 16:07     ` Reiser4 bug mjt
2004-09-05 16:07       ` Markus   Törnqvist
2004-09-08 17:53     ` Scheduler experiences (with Reiser4 bug report) Bill Davidsen

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=20040905142502.GQ26192@nysv.org \
    --to=mjt@nysv.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.