From: jlnance@intrex.net
To: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: Ongoing 2.4 VM suckage
Date: Fri, 3 Aug 2001 09:07:03 -0400 [thread overview]
Message-ID: <20010803090703.B1248@bessie.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0108021508310.21298-100000@heat.gghcwest.com> <Pine.LNX.4.33L.0108021925460.5582-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0108021925460.5582-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Thu, Aug 02, 2001 at 07:27:42PM -0300
On Thu, Aug 02, 2001 at 07:27:42PM -0300, Rik van Riel wrote:
> On Thu, 2 Aug 2001, Jeffrey W. Baker wrote:
>
> > I'm telling you that's not what happens. When memory pressure
> > gets really high, the kernel takes all the CPU time and the box
> > is completely useless. Maybe the VM sorts itself out but after
> > five minutes of barely responding, I usually just power cycle
> > the damn thing. As I said, this isn't a classic thrash because
> > the swap disks only blip perhaps once every ten seconds!
>
> What kind of workload are you running ?
>
> We could be dealing with some weird artifact of
> virtual page scanning here, or with a strange
> side effect of recent VM changes ...
Rik,
FWIW, I am seeing this sort of thing too, though I am running a 2.4.5
kernel so I am a little out of date. Its a large machine with 2G of ram,
4G of swap, and 2 CPUs. You dont have to actually use all the memory either.
When my process gets to about 1.5G and starts doing lots of file I/O, the
machine can just disappear for several minutes. I will be sshed in and
I can not even get my shell to give me a new prompt when I hit return. It
will eventually sort it self out, but it might take 15 minutes. I will try
and get a more recent kernel installed, but the machine is not under my
control, so I dont get to decide when that happens.
Thanks,
Jim
next prev parent reply other threads:[~2001-08-03 13:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 18:29 Jeffrey W. Baker
2001-08-02 18:52 ` Richard B. Johnson
2001-08-02 19:10 ` Jeffrey W. Baker
2001-08-02 19:54 ` Richard B. Johnson
2001-08-02 20:10 ` Jeffrey W. Baker
2001-08-02 20:16 ` Rik van Riel
2001-08-02 20:28 ` Rik van Riel
2001-08-03 17:59 ` David Ford
2001-08-03 20:53 ` Rik van Riel
2001-08-03 21:59 ` Mike Black
2001-08-03 22:08 ` Rik van Riel
2001-08-04 1:06 ` Daniel Phillips
2001-08-03 23:58 ` [PATCH] Disable kswapd through proc (was Ongoing 2.4 VM suckage) Daniel Phillips
2001-08-04 7:21 ` Ongoing 2.4 VM suckage Stephen Satchell
2001-08-06 8:55 ` Helge Hafting
2001-08-06 16:37 ` Jeremy Linton
2001-08-07 7:51 ` David Weinehall
2001-08-03 22:47 ` David Ford
2001-08-02 21:01 ` Richard B. Johnson
2001-08-02 21:11 ` Jeffrey W. Baker
2001-08-02 21:44 ` Jakob Østergaard
2001-08-02 21:52 ` Jeffrey W. Baker
2001-08-02 21:56 ` Miles Lane
2001-08-02 22:05 ` Jeffrey W. Baker
2001-08-02 22:07 ` Rik van Riel
2001-08-02 22:17 ` Jeffrey W. Baker
2001-08-02 22:27 ` Rik van Riel
2001-08-02 22:32 ` Jeffrey W. Baker
2001-08-02 22:56 ` BERECZ Szabolcs
2001-08-03 13:07 ` jlnance [this message]
2001-08-03 13:31 ` Richard B. Johnson
2001-08-06 13:22 ` Luigi Genoni
2001-08-06 13:29 ` David S. Miller
2001-08-02 23:46 ` Ongoing 2.4 VM suckage pagemap_lru_lock Jeremy Linton
2001-08-02 22:15 ` Ongoing 2.4 VM suckage Pavel Zaitsev
2001-08-02 22:20 ` Jakob Østergaard
2001-08-03 12:04 ` Anders Peter Fugmann
2001-08-03 16:03 ` Rik van Riel
2001-08-03 16:24 ` Anders Peter Fugmann
2001-08-03 21:24 ` Rik van Riel
2001-08-03 22:00 ` Anders Peter Fugmann
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=20010803090703.B1248@bessie.localdomain \
--to=jlnance@intrex.net \
--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®