From: Per Jessen <per@computer.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.28 - kswapd excessive cpu usage under heavy IO
Date: Mon, 6 Dec 2004 12:14:48 +0100 [thread overview]
Message-ID: <200412061214.48754.per@computer.org> (raw)
(apologies if this is sent more than once)
I've found similar incidences in the archives, but none that indicates that a
solution was found.
I'm seeing excessive cpu usage by kswapd on a 4way 500MHZ Xeon with 2GB RAM. A
find in a directory containing perhaps 6-700,000 files makes the box almost
grind to a halt. In 12days uptime, kswap has used 590:43.82, and during the
find-exercise usually runs with 90-100% util.
The file-system is 150GB with JFS117 on a software-RAID5 - not exactly optimal,
I agree, but reasonably workable.
I've read that 2.6 has significant improvements in this area, but upgrading is
not currently an option.
All hints & suggestions much appreciated.
--
Per Jessen, Zurich
http://www.spamcek.com - let your spam stop here.
next reply other threads:[~2004-12-06 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 11:14 Per Jessen [this message]
2004-12-06 12:57 ` 2.4.28 - kswapd excessive cpu usage under heavy IO Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 9:14 Per Jessen
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=200412061214.48754.per@computer.org \
--to=per@computer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.