From: Nick Piggin <piggin@cyberone.com.au>
To: bee71e@netscape.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: excessive swapping in 2.4.x
Date: Thu, 18 Sep 2003 15:39:21 +1000 [thread overview]
Message-ID: <3F694509.60100@cyberone.com.au> (raw)
In-Reply-To: <7E768FF1.7BC13987.0005DAE9@netscape.net>
bee71e@netscape.net wrote:
>Hi,
>
>I am using 2.4.21 and I see an unusually large amount of swapping for relatively low load :
>
>sample vmstat output: (note that the system is almost idle)
>
> procs memory swap io system cpu
>r b w swpd free buff cache si so bi bo in cs us sy id
>0 2 0 1850220 10524 9412 703652 3030 1102 3912 1106 1506 1710 1 1 98
>0 2 0 1849188 10572 9388 700568 2780 376 3558 379 1434 1284 1 1 99
>0 5 0 1851576 11668 9404 698228 2999 479 3890 488 1499 1487 1 1 98
>
>Is this a known issue? Whats happening? How do I fix this?
>
You could try the latest 2.4 prerelease. It has some VM updates.
next prev parent reply other threads:[~2003-09-18 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 1:07 excessive swapping in 2.4.x bee71e
2003-09-18 5:39 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-18 20:28 bee71e
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=3F694509.60100@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=bee71e@netscape.net \
--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