From: Javier Marcet <jmarcet@pobox.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Exaggerated swap usage && -aa lockup
Date: Sat, 30 Nov 2002 15:02:04 +0100 [thread overview]
Message-ID: <20021130140204.GA15565@jerry.marcet.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.44L.0211292349550.15981-100000@imladris.surriel.com>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
* Rik van Riel <riel@conectiva.com.br> [021130 02:57]:
>> root # vmstat 1
>> procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
>> r b swpd free buff cache si so bi bo in cs us sy id wa
>> 0 1 265048 5248 32248 119108 6 15 65 62 252 585 21 6 73 0
>> 1 6 266648 4480 32316 120300 0 4656 2152 4652 1348 821 13 8 79 0
>> 1 0 265052 4496 31036 120184 8 336 1668 340 1226 765 15 7 78 0
>> 0 1 265052 4496 31112 121564 4 0 3152 0 1198 894 18 8 74 0
>> 1 0 265052 4504 31076 123112 0 0 3024 8576 1229 857 17 7 76 0
> ^^^^^^^^^^^^^^^^^^^
>Looks like my guess was right after all. The amount of swap
>IO is maybe 10% of the amount of filesystem IO in your vmstat
>snippet above.
[...]
>Two things could be happening here:
>1) the kernel decides to cache the wrong things in the
> page cache
>and/or
>2) the IO scheduler is giving worse latencies now
>If the problem is (1) it might get resolved by using the -rmap
>or -aa kernels. If the problem is (2) you'll want Andrew Morton's
>read_latency patch (which I'll port to 2.4.20 real soon now).
I tend to believe is (1). I was using 2.4.20-jam0 (-aa derived) all this
morning. It seemed to behave better than 2.4.20-rc4-ac1 on this point. I
compiled a couple apps without problems, had different apps and servers
running while both si & so and bi & bo were low. However, when I was
uncompressing mozilla-1.2.tar.gz the system locked up, just as
2.4.20-rc2aa1 did days before. ALT-SYSRQ allowed me to reboot, but I did
not take note of any kernel dump...
I am now running 2.5.47-ac6 and things are _way_ better in any aspect.
I'll post some vmstat output later when the system has been running for
a while. So far it has already uncompressed mozilla's source with no
slowdown or lockup.
--
Javier Marcet <jmarcet@pobox.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2002-11-30 13:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 11:54 Exaggerated swap usage Javier Marcet
2002-11-29 12:20 ` Christer Nilsson
2002-11-29 16:31 ` Rik van Riel
2002-11-30 1:38 ` Javier Marcet
2002-11-30 1:55 ` Rik van Riel
2002-11-30 2:47 ` Zwane Mwaikambo
2002-11-30 5:17 ` Javier Marcet
2002-11-30 14:02 ` Javier Marcet [this message]
2002-11-30 2:42 ` Zwane Mwaikambo
2002-11-30 3:02 ` Andrew Morton
2002-11-30 4:12 ` Zwane Mwaikambo
2002-11-30 6:48 ` khromy
2002-11-30 6:49 ` Javier Marcet
2002-11-30 7:08 ` Dmitri
2002-11-30 14:05 ` Javier Marcet
2002-11-30 18:23 ` khromy
2002-11-30 18:43 ` Andrea Arcangeli
2002-12-01 7:39 ` Javier Marcet
2002-12-01 7:53 ` Javier Marcet
2002-12-01 10:34 ` Andrea Arcangeli
2002-12-01 7:59 ` Javier Marcet
2002-12-01 10:36 ` Andrea Arcangeli
2002-12-01 14:37 ` Nuno Monteiro
2002-12-02 0:21 ` Andrea Arcangeli
2002-12-02 1:01 ` Nuno Monteiro
2002-12-02 4:55 ` Javier Marcet
2002-12-02 21:24 ` Andrew Clayton
2002-11-30 14:05 ` Steffen Moser
2002-11-30 18:22 ` Rik van Riel
2002-12-01 7:57 ` Javier Marcet
2002-12-01 19:27 ` Rik van Riel
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=20021130140204.GA15565@jerry.marcet.dyndns.org \
--to=jmarcet@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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®