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: Fri, 30 Mar 2007 00:39:23 -0400 [thread overview]
Message-ID: <75b66ecd0703292139m371e023xc17b3124ef991919@mail.gmail.com> (raw)
In-Reply-To: <20070330035457.57A4124753@ws5-3.us4.outblaze.com>
On 3/29/07, Elliott Johnson <ejohnson@linuxmail.org> wrote:
> >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
>
> Well the problem is apparent, we are having abnormally high cpu usage. It's about a
> 20-40% performance hit.
>
Please post a kernel profile for the problematic workload with the
"good" and "bad" kernels (search the list archive for Andrew Morton's
instructions on doing it with oprofile, email me privately if you
can't find it).
> The vmstat man page has little information on this statistic and there seems to be varying
> explanations on the web. I was hoping for a decisive explanation (or link) and possibly
> advice in toggling this value (or reasons not to).
The meaning of these numbers can change drastically from one minor
release to the next, and the docs often lag behind the code.
I would not focus on tweaking VM knobs, but on describing the problem
in enough detail to fix the kernel - it's a bug if the same workload
regresses significantly from one release to another.
Lee
next prev parent reply other threads:[~2007-03-30 4:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 3:54 Elliott Johnson
2007-03-30 4:39 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-31 2:08 Elliott Johnson
2007-03-29 22:22 Elliott Johnson
2007-03-30 2:14 ` Lee Revell
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=75b66ecd0703292139m371e023xc17b3124ef991919@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®