mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc5: multiuser scheduling trouble
Date: Sat, 10 Dec 2005 17:27:59 +0100	[thread overview]
Message-ID: <20051210162759.GA15986@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.64.0512032155290.3099@g5.osdl.org>

2.6.15-rc5 (and earlier 2.6 kernels) seems to have a slight scheduling 
problem, with some starvation at a load of only 2.

All it takes is two users with separate X desktops.
User one plays flash games using firefox. The ill-designed flash stuff
typically means that his Xorg and firefox divides the cpu 100% between them.

So I expect that I, as user two, should notice some slowness. I should get only
1/2 - 1/3 cpu.  But I get periods of starvation.  Logging in takes a long time,
bringing iup icewm takes 15s instead of 2, each xterm takes a long time to
start.  They are usually instantaneous.  Tha machine is unsuitable
for work in this mode.

Knowing the root password I renices his Xorg and firefox by 10, and then
everything is fine.  His games are still ok, and my xterms are snappy again.

I have tried no preempt, voluntary preempt, and preemptible kernel.  It doesn't
make a difference.  This is an amd64 kernel on an opteron 244 (1800MHz).  Everyhting
is 64-bit except firefox+flash which is 32-bit.

Perhaps the way flash games work, with lots of communication with the xserver,
makes them get "io boost" even though they are cpu hogs. I still think
my xterm (or whatever I am starting up) should get its fair third of the cpu
though, (with firefox and xorg hogging one third each too.)  Even a "600MHz opteron"
ought to do better than this.

The machine isn't trashing, it is hardly touching swap.  (512M memory, and swpd=16 
according to vmstat) The paging-in of a starting executable shouldn't be affected much
by the cpu load?

Helge Hafting

  parent reply	other threads:[~2005-12-10 16:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04  6:03 Linux 2.6.15-rc5: off-line for a week Linus Torvalds
2005-12-04 15:34 ` Gene Heskett
2005-12-04 18:50   ` Michael Krufky
2005-12-04 20:47     ` Gene Heskett
2005-12-04 21:14       ` Michael Krufky
2005-12-05  0:16         ` Gene Heskett
2005-12-04 16:56 ` Jesper Juhl
2005-12-04 17:26   ` Michal Piotrowski
2005-12-04 18:35     ` Jesper Juhl
2005-12-04 22:25       ` Andrea Arcangeli
2005-12-04 23:43 ` Linux 2.6.15-rc5: sk98lin broken Johannes Stezenbach
2005-12-05 19:00   ` [PATCH linux-2.6.15-rc5] sk98lin: rx checksum offset not set Stephen Hemminger
2005-12-05 19:22     ` Johannes Stezenbach
2005-12-05 19:13   ` Linux 2.6.15-rc5: sk98lin broken Bill Davidsen
2005-12-07 21:59 ` Linux 2.6.15-rc5: off-line for a week Rich Walker
2005-12-10 16:27 ` Helge Hafting [this message]
2005-12-12  0:09   ` Linux 2.6.15-rc5: multiuser scheduling trouble Linus Torvalds
2005-12-12  6:51     ` Ingo Molnar
2005-12-12 11:18       ` Helge Hafting
2005-12-12 11:30       ` Nix
2005-12-12 12:31         ` Helge Hafting
2005-12-12 10:51     ` Helge Hafting
2005-12-10 21:23 ` Linux 2.6.15-rc5 bad page with fglrx on Radeon X300 Brice Goglin
2005-12-10 21:43   ` Lee Revell
2005-12-11 10:49   ` Hugh Dickins

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=20051210162759.GA15986@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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®