From: Ingo Ciechowski <ciechowski@cis-computer.com>
To: "Dan Maas" <dmaas@dcine.com>
Cc: linux-kernel@vger.kernel.org, stimits@idcomm.com
Subject: Re: High system CPU% in dual CPU System
Date: Sat, 23 Jun 2001 06:53:33 +0200 [thread overview]
Message-ID: <p05100323b759d0c24582@[194.162.209.20]> (raw)
In-Reply-To: <014301c0fb94$217aee50$1a01a8c0@allyourbase>
In-Reply-To: <fa.h2turhv.121c3bs@ifi.uio.no> <014301c0fb94$217aee50$1a01a8c0@allyourbase>
At 23:25 Uhr -0400 22.06.2001, Dan Maas wrote:
> > CPU0 states: 19.2% user, 32.0% system, 0.0% nice, 48.2% idle
>> CPU1 states: 20.4% user, 40.1% system, 0.0% nice, 38.3% idle
>
>> What can I do to find out what the CPUs are doing during "system" time?
>
>Try 'ps -ax' and see if any process has a large TIME (cumulative CPU time).
>I suspect you may just be seeing a kernel idle process (e.g. kapm-idled),
>which is nothing to worry about.
Hi Dan,
thanx for the hint. I could identify one of my scripts as cause of
the problem and will now have a closer look at its periodic activity..
Ingo
next parent reply other threads:[~2001-06-23 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <014301c0fb94$217aee50$1a01a8c0@allyourbase>
[not found] ` <fa.h2turhv.121c3bs@ifi.uio.no>
2001-06-23 4:53 ` Ingo Ciechowski [this message]
2001-06-22 22:35 Ingo Ciechowski
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='p05100323b759d0c24582@[194.162.209.20]' \
--to=ciechowski@cis-computer.com \
--cc=dmaas@dcine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stimits@idcomm.com \
/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®