From: Kasper Sandberg <lkml@metanurb.dk>
To: hechacker1 <hechacker1@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "REPORT: sd-0.46 vs cfs-v6 vs mainline 2.6.21-rc7 Beryl + Video + Audio"
Date: Fri, 27 Apr 2007 10:42:04 +0200 [thread overview]
Message-ID: <1177663324.29963.4.camel@localhost> (raw)
In-Reply-To: <6700d24e0704262101v132bec29nf9fd6c93fe8748a@mail.gmail.com>
On Thu, 2007-04-26 at 21:01 -0700, hechacker1 wrote:
<snip>
> Overall:
> SD-0.46 is my new choice for scheduler. When not under load everything
> run's better or similarly to cfs or mainline. Under load however it
> shows the most responsiveness.
>
> Occasionally I had complete mouse freezes with cfs when the system was
> busy. But rarely.
>
> Under SD i haven't seen anything get starved.
>
> mainline surprisingly works better than i expected, but beryl suffers
> and responsiveness suffers under load.
Your findings seems somewhat similar to mine, what i have observed is
that SD is much more smooth, with vanilla/cfs, under just abit load
opengl stuff will stutter, whereas with sd it will simply get
slightly(or more, depending on the load) lower fps.
>
> --hechacker1
> -
> 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/
>
next prev parent reply other threads:[~2007-04-27 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 4:01 "REPORT: sd-0.46 vs cfs-v6 vs mainline 2.6.21-rc7 Beryl + Video + Audio" hechacker1
2007-04-27 8:42 ` Kasper Sandberg [this message]
2007-04-27 14:05 ` Ingo Molnar
2007-04-28 1:09 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 8:39 hechacker1
2007-04-30 0:21 ` hechacker1
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=1177663324.29963.4.camel@localhost \
--to=lkml@metanurb.dk \
--cc=hechacker1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox