mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Gerdau <mgd@technosis.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.22.2-cfs-v19.1 stops honouring nice 3 after some hours
Date: Wed, 15 Aug 2007 18:23:17 +0200	[thread overview]
Message-ID: <200708151823.17623.mgd@technosis.de> (raw)

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

Hi Ingo,

I played a bit with renicing my (mostly) CPU bound jobs and found
somewhat strange behaviour.

I'm on 2.6.22.2-cfs-v19.1 -- I can't boot into 2.6.23-rc3 as part of
my daily work because my NVIDIA driver doesn't yet work with it though
I could try to do some X-less testing if need be.

I'm running 4 CPU bound jobs, 2 of which are more important to me.
I therefor reniced the other 2 to level 3 and the CPU percentages
were roughly 66/66/33/33 on my Dualcore system. So far all fine.

Some 6 hours later I rechecked with top -d 60 and got the output below:

19629 mgd       20   0  334m 263m 2700 R   49  8.1  69:16.45 perl
29668 mgd       20   0  396m 262m 2700 R   49  8.0 112:17.21 perl
 6933 mgd       23   3 96576  21m 3672 R   47  0.7  46:38.83 perl
14162 mgd       23   3  165m  28m 3672 R   47  0.9 194:55.31 perl

I reniced to 0:

19629 mgd       20   0  334m 263m 2700 R   48  8.1  71:02.86 perl
 6933 mgd       20   0 96652  21m 3672 R   48  0.7  48:23.41 perl
14162 mgd       20   0  165m  28m 3676 R   48  0.9 196:39.81 perl
29668 mgd       20   0  396m 262m 2700 R   48  8.0 114:03.56 perl

...and back to 3 with no noticeable change.

[at this point job 14162 finished and was replaced by an similar
job 22558]

I then decided to do some statistics and reniced to 1:

29668 mgd       20   0  396m 262m 2700 R   48  8.0 115:24.12 perl
19629 mgd       20   0  334m 263m 2700 R   48  8.1  72:23.36 perl
22558 mgd       21   1 92184  17m 3672 R   48  0.5   0:56.81 perl
 6933 mgd       21   1 96576  21m 3672 R   48  0.7  49:54.12 perl

Now I reniced to 2 and without knowing why, the ratios seem to be back
to where I want them.

29668 mgd       20   0  396m 262m 2700 R   59  8.0 116:33.98 perl
19629 mgd       20   0  334m 264m 2700 R   58  8.1  73:31.49 perl
22558 mgd       22   2 92220  17m 3672 R   37  0.5   1:46.99 perl
 6933 mgd       22   2 96688  21m 3672 R   36  0.7  50:44.77 perl

Renicing to 3 again gives me what I want:

29668 mgd       20   0  397m 262m 2700 R   65  8.0 117:25.93 perl
19629 mgd       20   0  334m 264m 2700 R   63  8.1  74:21.84 perl
22558 mgd       23   3 92220  17m 3672 R   32  0.5   2:13.83 perl
 6933 mgd       23   3 96652  21m 3672 R   32  0.7  51:11.24 perl


I don't know why I had the very first output above though.

Best,
Michael
-- 
 Technosis GmbH, Geschäftsführer: Heiko 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 --]

             reply	other threads:[~2007-08-15 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 16:23 Michael Gerdau [this message]
2007-08-16 17:52 ` Peter Zijlstra
2007-08-16 18:36   ` Michael Gerdau
2007-08-20  7:54   ` Michael Gerdau

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=200708151823.17623.mgd@technosis.de \
    --to=mgd@technosis.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome