From: Michael Gerdau <mgd@technosis.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
Miguel Figueiredo <elmig@debianpt.org>,
Ray Lee <ray-lk@madrabbit.org>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: Sched - graphic smoothness under load - cfs-v13 sd-0.48
Date: Wed, 23 May 2007 07:23:23 +0200 [thread overview]
Message-ID: <200705230723.42400.mgd@technosis.de> (raw)
In-Reply-To: <200705241036.45179.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
> That's because the whole premise of your benchmark relies on a workload that
> yield()s itself to the eyeballs on most graphic card combinations when using
> glxgears. Your test remains a test of sched_yield in the presence of your
> workloads rather than anything else. If people like ck2 it's because in the
> real world with real workloads it is better, rather than on a yield() based
> benchmark. Repeatedly the reports are that 3d apps and games in normal usage
> under -ck are better than mainline and cfs.
While I can't comment on the technical/implementational details of
Con's claim I definitely have to agree from a users POV.
All my recent CPU intensive benchmarks show that both ck/sd and cfs
are very decent scheduler and IMO superior to mainline for all _my_
usecases. In particular playing supertux while otherwise fully utilizing
both CPUs on a dualcore works without any glitch and better than
on mainline for both sd and cfs.
For me the huge difference you have for sd to the others increases the
likelyhood the glxgears benchmark does not measure scheduling of graphic
but something else.
Anyway, I'm still in the process of collecting data or more precisely
until recently constantly refined what data to collect and how. I plan
to provide new benchmark results on CPU intensive tasks in a couple of
days.
Best,
Michael
--
Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: mgd@technosis.de
GPG-keys available on request or at public keyserver
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-23 5:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 20:02 Sched - graphic smoothness under load - cfs-v13 sd-0.48 Bill Davidsen
2007-05-19 20:22 ` Ray Lee
2007-05-20 0:44 ` Bill Davidsen
2007-05-20 6:12 ` Michael Gerdau
2007-05-20 6:30 ` Ray Lee
2007-05-20 6:59 ` Michael Gerdau
2007-05-20 7:20 ` Ray Lee
2007-05-20 6:55 ` Ray Lee
2007-05-21 18:27 ` Matt Keenan
2007-05-19 20:36 ` Diego Calleja
2007-05-19 20:55 ` Ray Lee
2007-05-19 23:21 ` Mike Galbraith
2007-05-20 16:29 ` Miguel Figueiredo
2007-05-20 16:44 ` Ray Lee
2007-05-20 16:58 ` Miguel Figueiredo
2007-05-20 17:19 ` Ray Lee
2007-05-22 17:55 ` Bill Davidsen
2007-05-22 20:01 ` Miguel Figueiredo
2007-05-23 0:28 ` Bill Davidsen
2007-05-23 13:10 ` Bill Davidsen
2007-05-23 18:29 ` Miguel Figueiredo
2007-05-23 20:45 ` Bill Davidsen
2007-05-23 21:03 ` Miguel Figueiredo
2007-05-24 0:36 ` Con Kolivas
2007-05-23 4:06 ` William Lee Irwin III
2007-05-23 5:23 ` Michael Gerdau [this message]
2007-05-23 7:58 ` Xavier Bestel
2007-05-23 8:21 ` Bill Huey
2007-05-23 18:22 ` Ian Romanick
2007-05-23 18:43 ` Xavier Bestel
2007-05-23 17:22 ` Bill Davidsen
2007-05-23 16:59 ` Bill Davidsen
2007-05-22 17:22 ` 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=200705230723.42400.mgd@technosis.de \
--to=mgd@technosis.de \
--cc=davidsen@tmr.com \
--cc=elmig@debianpt.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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