public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linus 2.6.23-rc1
Date: Sun, 29 Jul 2007 02:40:31 +0200	[thread overview]
Message-ID: <1185669631.1432.2.camel@localhost> (raw)
In-Reply-To: <200707290141.19790.volker.armin.hemmann@tu-clausthal.de>

On Sun, 2007-07-29 at 01:41 +0200, Volker Armin Hemmann wrote:
> Hi,
> 
> I never tried Con's patchset, for two reasons:
> I tried his 2.4 patches ones, and I never saw any improvements. So when people 
> were reporting huge improvements with his SD scheduler, I compared that with 
> the reports of huge improvements with his 2.4 kernel patches.

Well thats a reason if there ever were one...

> ...
> The second: too many patches. I only would have tried one or two, but the 
> ck-patchset is a lot bigger.. and I am a little bit uneasy about that.

so use only the scheduler? nobody forces you to do many things..

> 
> But I tried a lot of Ingo's cfs patches - and it was a very pleasant 
> experience. Ingo reacted very fast on my feedback and when I hit a problem he 
> really tried to find the cause and solve it - and it always was one patch, so 
> I felt a lot less scared ;)
> 
> My usual workload is very 'usual'. KDE desktop, kmail, konqueror, sometimes 
> xine or amarok providing some background noise while typing away in kate, 
> triplea, wesnoth or some other game when I need to 'rest' for a while. A lot 
> of compiling in the background, because I am one of these gentoo users.
> 
> With cfs the experience was much more pleasant than with the 'old' scheduler. 
> Compiling did not hurt as much as usual anymore - the only thing that hurts 
> is swap.... 
> 
> But there is another thing I do regularly: I play ut2004. Not every single 
> day, but sometimes several times a day. 20minutes of mayhem and then back to 
> the desktop.
> 
> And I do not see any problems with cfs and ut2004. The maximum FPS are indeed 
> a little bit lower (and you can argue that this really is not important if 
> the pre-game FPS in a level looking down on the floor go down from 390 to 
> 380FPS), but the minimum FPS went up!

well, surely CFS is better than the old vanilla scheduler, also with 3d,
and if you have that high fps, i doubt you will notice the effects me
and others are having. it is not that it is bad, its just not as good as
SD has shown to be possible..

> 
> In scenes when my system is fighting hard to provide the FPS, when the action 
> is high (like when fighting with half a douzend bots at a power node, while 
> some other bots are shooting into the mess) CFS is much better than the old 
> scheduler. It is a big difference if you get 6-10FPS or 15-25.
> (I am playing with maximum 'beautifullness' - I would be able to get a lot 
> more FPS, if I wanted, but I want a nice scenery and maximum visual 
> effects ...)
> 
> From my point of view 3D is a lot better with cfs. 

Better than old vanilla yes, but than SD? well, you should give it a
try.

> 
> Now the question for all the people who are bashing cfs for its bad 3d 
> performance: what am I doing wrong?

As said, we never said CFS was worse than old vanilla, and we never said
it was BAD, we did however say its not as good as SD :)

> 
> Glück Auf,
> Volker
> 
> -
> 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/


  reply	other threads:[~2007-07-29  0:43 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-28 23:41 Linus 2.6.23-rc1 Volker Armin Hemmann
2007-07-29  0:40 ` Kasper Sandberg [this message]
2007-07-29 15:20   ` Volker Armin Hemmann
  -- strict thread matches above, loose matches on Subject: below --
2007-07-22 21:04 Linus Torvalds
2007-07-22 22:10 ` Andre Noll
2007-07-22 22:22   ` Andi Kleen
2007-07-22 23:23     ` Andre Noll
2007-07-22 23:31       ` Andi Kleen
2007-07-23  6:07         ` Jakub Jelinek
2007-07-22 23:33 ` Alistair John Strachan
2007-07-22 23:51   ` Roland McGrath
2007-07-23  0:07     ` Adrian Bunk
2007-07-23  0:31       ` Roland McGrath
2007-07-23  1:43         ` Adrian Bunk
2007-07-23  1:20 ` Gabriel C
2007-07-23  1:23 ` Paul Mundt
2007-07-23  1:27   ` Gabriel C
2007-07-23  1:40     ` Paul Mundt
2007-07-23  4:11   ` Greg KH
2007-07-23  2:48 ` Gabriel C
     [not found] ` <46A40BC7.9030209@googlemail.com>
2007-07-23  2:42   ` Gabriel C
2007-07-23 15:47   ` Bob Picco
2007-07-23 15:54     ` Luck, Tony
2007-07-23 16:43 ` Gabriel C
2007-07-23 16:57   ` Ismail Dönmez
2007-07-23 20:44     ` Alessandro Suardi
2007-07-24 14:49       ` Len Brown
2007-07-28  2:04 ` Kasper Sandberg
2007-07-28  2:35   ` Linus Torvalds
2007-07-28  9:44     ` Kasper Sandberg
2007-07-28 17:50       ` Linus Torvalds
2007-07-28 18:07         ` Kasper Sandberg
2007-07-28 19:13         ` Jan Engelhardt
2007-07-28 19:34           ` Linus Torvalds
2007-07-28 21:33             ` Linus Torvalds
2007-07-28 21:55               ` Jan Engelhardt
2007-07-28 22:22                 ` Linus Torvalds
2007-08-01  9:21             ` Jan Engelhardt
2007-07-29 15:04   ` Ingo Molnar
2007-07-29 23:04     ` George Sescher
2007-07-29 23:18       ` Linus Torvalds
2007-07-29 23:38         ` George Sescher
2007-07-29 23:58           ` Linus Torvalds
2007-07-31 10:05         ` Bill Huey
2007-07-31 14:04           ` Ingo Molnar
2007-07-31 15:44           ` Linus Torvalds
2007-07-30  6:44       ` Ingo Molnar
2007-07-30  7:06         ` George Sescher
2007-07-30  7:55           ` Ingo Molnar
2007-07-30  9:26             ` George Sescher
2007-07-30 10:26               ` Ingo Molnar
2007-07-30 16:13     ` Kasper Sandberg
2007-07-28 14:52 ` Ronni Nielsen
2007-07-28 17:30   ` Linus Torvalds

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=1185669631.1432.2.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=volker.armin.hemmann@tu-clausthal.de \
    /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