From: "Lee Revell" <rlrevell@joe-job.com>
To: "Elliott Johnson" <ejohnson@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange high system cpu usage.
Date: Thu, 29 Mar 2007 22:14:46 -0400 [thread overview]
Message-ID: <75b66ecd0703291914n551b49d8n93cfbb3374ba8752@mail.gmail.com> (raw)
In-Reply-To: <20070329222221.9C53BCA0A4@ws5-11.us4.outblaze.com>
On 3/29/07, Elliott Johnson <ejohnson@linuxmail.org> wrote:
> Hello,
>
> I've been upgrading a few machines here at work and noticed some problems with high system cpu usage on one machine. In trying to debug the problem I've come across a few confusing stats that I was hoping could be cleared up by someone on this list.
What problem are you trying to solve? IOW, how do you know it's not
just an artifact of diferent load average calculation between 2.4 and
2.6?
Are you actually seeing reduced throughput/performance? Or are you
just looking at load average?
Lee
next prev parent reply other threads:[~2007-03-30 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 22:22 Elliott Johnson
2007-03-30 2:14 ` Lee Revell [this message]
2007-03-30 3:54 Elliott Johnson
2007-03-30 4:39 ` Lee Revell
2007-03-31 2:08 Elliott Johnson
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=75b66ecd0703291914n551b49d8n93cfbb3374ba8752@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=ejohnson@linuxmail.org \
--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®