From: DaMouse <damouse@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler experiences
Date: Sun, 5 Sep 2004 13:25:30 +0100 [thread overview]
Message-ID: <1a56ea390409050525583d0438@mail.gmail.com> (raw)
In-Reply-To: <1094386464.18114.0.camel@localhost>
On Sun, 05 Sep 2004 14:14:24 +0200, Kasper Sandberg <lkml@metanurb.dk> wrote:
> Hey, i wonder which scheduler you people have the best experiences with,
> staircase or nicksched?
>
> personally i were using nicksched for a long time, but then i tried
> staircase, and i like it overall more,
>
> with nicksched its like, 1 process gets good prioity, so that if tvtime
> is running, it runs perfect, but moving windows and stuff will be not so
> fluid.
> with staircase, the overall performance is not as fast, but
> interactivity is really good, like tvtime runs fine, moving windows are
> fast as lightening, setiathome can also run perfect.
>
> --
> Kasper Sandberg <lkml@metanurb.dk>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
I personally like staircase, i also used to use nicksched but i prefer
staircases simple design and structure. Nicksched was pretty fast but
twiddling around all day with renicing X and now the HT issues are
annoying and staircase has always worked perfectly for me without
flipping fifty switches in the cockpit.
-DaMouse
--
I know I broke SOMETHING but its there fault for not fixing it before me
next prev parent reply other threads:[~2004-09-05 12: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 [this message]
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
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=1a56ea390409050525583d0438@mail.gmail.com \
--to=damouse@gmail.com \
--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.