From: Piotr Neuman <sikkh@wp.pl>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler experiences
Date: Sun, 5 Sep 2004 14:49:24 +0200 [thread overview]
Message-ID: <200409051449.24392.sikkh@wp.pl> (raw)
In-Reply-To: <1094386464.18114.0.camel@localhost>
> Hey, i wonder which scheduler you people have the best experiences with,
> staircase or nicksched?
I'm using staircase exclusively, but I did compare it to vanilla kernel's
scheduler and yes the interactivity is very good (I'm running x.org and KDE
3.2.3 here).
I have had no sound skips or tvtime problems no matter what kind of disk IO
was being done, which includes MySQL database updates, cron scripts (running
rpm -V on all packages) and wwwoffle purging cached files (note I use the
default as IO sched). Also kernel compilation is no threat to interactivity
with staircase.
I'm a Mandrake user and since the release of Mandrake 10 it does not renice X
server to higher priority so I guess Nick's scheduler would force me to tweak
X startup script.
The other things I like about staircase are that it gives you kernel.compute
and kernel.interactive sysctls that allow to perform serious computational
tasks with it. Also ability to use scheduling policies with schedtool is a
great plus, for example using SCHED_BATCH for cpu bound applications like
seti@home or folding@home.
Overall staircase has been a great experience for me.
Regards
Piotr Neuman
next prev parent reply other threads:[~2004-09-05 12:49 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 [this message]
2004-09-05 14:25 ` Markus Törnqvist
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=200409051449.24392.sikkh@wp.pl \
--to=sikkh@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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.