From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3-mm1 interactivity scheduling mistakes (smp)
Date: Wed, 13 Aug 2003 20:08:21 +0200 [thread overview]
Message-ID: <1060798101.603.47.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <20030813180020.GA1339@hh.idb.hist.no>
On Wed, 2003-08-13 at 20:00, Helge Hafting wrote:
> I ran a "nice make -j3 bzImage" on 2.6.9-test3-mm1 in order
> to compile 2.6.0-test3-mm2 on my dual celeron.
>
> While waiting I played cuyo, a lightweight game similiar to tetris.
>
> This mostly behaved as expected, with a responsive game.
> But mozilla (on some other virtual desktop) occationally
> refreshed its page, causing several seconds with jerky response
> in the game.
>
> This is wrong for two reasons:
> 1. There should be enough cpu with two processors,
> one running the game and another the heavy mozilla stuff.
> The make was niced after all. No guessing, I told it explicitly.
>
> 2. The game has very interactive behaviour, it uses 4-10% cpu
> and cause X to use about 20%. Mozilla may have been idle for a
> while, getting "interactive". But it shouldn't remain
> interactive for so long, it sat at 100% till it went
> idle again.
>
> X runs with elevated priority, (std. debian testing setup)
> but that shouldn't matter - X only used 20% and that was
> for the game and two xterms. Mozilla wasn't visible
> at all.
I can't tell you why, but for me, X behaves horribly if it's not reniced
exactly at +0. In the past, I reniced X at -20, but Con told me that
with O??int patches, X must/should work with no nicing at all.
Could you please try again with X not reniced?
Thanks!
next prev parent reply other threads:[~2003-08-13 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 18:00 Helge Hafting
2003-08-13 18:08 ` Felipe Alfaro Solana [this message]
2003-08-14 11:16 ` Helge Hafting
2003-08-15 17:14 ` Helge Hafting
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=1060798101.603.47.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=helgehaf@aitel.hist.no \
--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
all inboxes | Powered by JetHome®