From: carlos@fisica.ufpr.br (Carlos Carvalho)
To: linux-kernel@vger.kernel.org
Subject: problem with nice values and cpu consumption in 2.6.11-5
Date: Tue, 3 May 2005 11:24:56 -0300 [thread overview]
Message-ID: <17015.35256.12650.37887@fisica.ufpr.br> (raw)
Look at this cpu usage in a two-processor machine:
893 user1 39 19 7212 5892 492 R 99.7 1.1 3694:29 mi41
1118 user2 25 0 155m 61m 624 R 50.0 12.3 857:54.18 b170-se.x
1186 user3 25 0 155m 62m 640 R 50.2 12.3 103:25.22 b170-se.x
The job with nice 19 seems to be using 100% of cpu time while the
other two nice 0 jobs share a single processor with 50% only. This is
persistent, not a transient. I did a kill -STOP to the nice 19 job and
a kill -CONT, and for a while it decreased the cpu usage but later
returned to the above.
This is with kernel 2.6.11-5 and top 3.2.5. What's the reason for this
(apparent??) mis-behavior and how can I correct it? This is important
because the machine is used for number-crunching and users get really
upset when they don't get the expected share of cpu time...
next reply other threads:[~2005-05-03 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 14:24 Carlos Carvalho [this message]
2005-05-04 11:52 ` Kirill Korotaev
2005-05-04 12:12 ` Con Kolivas
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=17015.35256.12650.37887@fisica.ufpr.br \
--to=carlos@fisica.ufpr.br \
--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®