From: Andrew Morton <akpm@digeo.com>
To: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: anticipatory scheduling questions
Date: Sun, 2 Mar 2003 12:43:58 -0800 [thread overview]
Message-ID: <20030302124358.5e4c4751.akpm@digeo.com> (raw)
In-Reply-To: <20030302114035.22346.qmail@linuxmail.org>
"Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> wrote:
>
> > You have not actually said whether 2.5.63 base exhibits
> > the same problem. From the vmstat traces it appears
> > that the answer is "yes"?
>
> Both 2.5.63 and 2.5.63-mm1 exhibit this behavior, but
> can't be reproduced with 2.4.20-2.54.
By 2.54 I assume you mean 2.5.54?
> > > I have retested this with 2.4.20-2.54, 2.5.63 and 2.5.63-mm1...
> > > and have attached the files to this message
> >
> > Thanks. Note how 2.4 is consuming a few percent CPU, whereas 2.5 is
> > consuming 100%. Approximately half of it system time.
>
> It seems is not "user" or "system" time what's being consumed, it's
> "iowait" Look below :-)
Your vmstat traces were showing tons of user time as well as system
time. Please make sure that you have the latest version of procps,
from http://surriel.com/procps/ or http://procps.sourceforge.net/
> > It does appear that some change in 2.5 has caused evolution to go berserk
> > during this operation.
>
> I wouldn't say it's exactly Evolution what's going berserk. Doing a
> "top -s1" while trying to reply to a big e-mail message, I've noticed
> that "top" reports "iowait" starting at ~50%, then going up very fast
> and then staying up at 90-95% all the time. This happens on 2.5.63
> and 2.5.63-mm1, however, on 2.4.20-2.54 kernel, "iowait" stays all
> the time exactly at "0%" and idle time remains steady at 90-95%.
Well certainly the IO stream _looks_ like it is stuck in IO-wait a lot.
It is strange that this has been happening for a couple of months and seems
to only affect Felipe Solana's copy of evolution. I still can't get my copy
to spellcheck a thing. I need to wrestle with it a bit more.
next prev parent reply other threads:[~2003-03-02 20:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 11:40 Felipe Alfaro Solana
2003-03-02 20:43 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-02 21:50 Felipe Alfaro Solana
2003-03-01 14:48 Felipe Alfaro Solana
[not found] <fa.g5ol5kg.cgoq0g@ifi.uio.no>
[not found] ` <fa.hp882fv.1u0orj9@ifi.uio.no>
2003-03-01 12:48 ` Ed Tomlinson
2003-03-01 10:25 Felipe Alfaro Solana
2003-03-01 10:40 ` Andrew Morton
2003-03-01 11:51 ` David Lang
2003-03-01 17:15 ` Alan Cox
2003-02-28 23:12 Felipe Alfaro Solana
2003-02-28 23:16 ` Andrew Morton
2003-02-28 14:38 Felipe Alfaro Solana
2003-02-28 19:14 ` Andrew Morton
2003-02-28 12:18 Felipe Alfaro Solana
2003-02-28 12:44 ` Andrew Morton
2003-02-27 22:24 Felipe Alfaro Solana
2003-02-27 23:26 ` Andrew Morton
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=20030302124358.5e4c4751.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=felipe_alfaro@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®