public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nico Schümann" <spam@nico22.de>
To: linux-kernel@vger.kernel.org
Cc: Mike Galbraith <efault@gmx.de>
Subject: Re: CFS not suitable for desktop computers
Date: Mon, 04 May 2009 17:16:32 +0200	[thread overview]
Message-ID: <49FF06D0.80109@nico22.de> (raw)
In-Reply-To: <1241424835.26855.102.camel@marge.simson.net>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Thank you Ray Lee and Mike Galbraith for your responses, I ran the 
script and attached its gathered information.

Mike Galbraith wrote:
> How hard is hard?  Can you describe the loads you're having trouble
> with, and the hardware you're running them on?
>
>   
I could reproduce "hard" load by just compiling the linux kernel, make 
-j3 while reading mails with Thunderbird, which is not that hard 
foreground load. Thunderbird starts reacting really slowly while compiling.

My system has a 1,3 GHz AMD Athlon CPU (32 bits) and 1 GB of RAM. Now 
you will say: That is not very much. Of course it is not, but with the 
old scheduler, the system felt way faster, so it seemed to be enough for 
compiling and reading mails.
I hope you can find useful information in the attached log, I enabled 
SCHED_DEBUG and SCHEDSTATS, if you need any more information, just ask 
me, I will try to answer.

And thank you all for your help,

Nico Schümann

[-- Attachment #2: cfs-debug-info-2009.05.04-17.04.35.gz --]
[-- Type: application/x-gzip, Size: 63145 bytes --]

  parent reply	other threads:[~2009-05-04 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 19:26 CFS not suitable for desktop computers Nico Schümann
2009-05-03 23:24 ` Ray Lee
     [not found] ` <1241424835.26855.102.camel@marge.simson.net>
2009-05-04 15:16   ` Nico Schümann [this message]
2009-05-04 17:59     ` Mike Galbraith
2009-05-04 21:01     ` Chris Friesen
2009-05-05  5:42       ` Mike Galbraith
2009-05-05  7:51         ` Mike Galbraith
2009-05-06  8:03     ` Peter Zijlstra

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=49FF06D0.80109@nico22.de \
    --to=spam@nico22.de \
    --cc=efault@gmx.de \
    --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