public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Boley <pboley@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: severe slowdown with 2.4 series w/heavy disk access
Date: Tue, 25 Dec 2001 05:37:40 -0500	[thread overview]
Message-ID: <3C2856F4.9BF7B835@home.com> (raw)
In-Reply-To: <3C295D5C.50EE365D@home.com> <01122609375800.01845@manta>

vda wrote:

> >
> >              total       used       free     shared    buffers
> > cached
> > Mem:        417472     412192       5280          0      20632
> > 315680
> > -/+ buffers/cache:      75880     341592
> > Swap:       136544          0     136544
> 
> It seems you think your memory is used for no purpose,
> but kernel just keeps page cache in your RAM (kernel bugs are indeed
> possible, but your test does not show any buggy behavior IMHO).

My whole system slows down (commands take a long time to execute,
decompression slows, ls in an empty dir takes 10 sec)

> 
> To verify this, you may repeat this experiment on a separate partition:
> 1) mount a partition
> 2) do the test as you described
> 3) umount the partition

I did this, and it uncached some, but I only had 60megs (out of 416)
free after unmounting the partition.  The cache went down to about 5
megs, and in-use was at 350 megs.

> 
> I believe you should see tons of free memory then, especially if your tarfile
> is also on that partition.
> Please report back if you would do the test.
> --
> vda

  parent reply	other threads:[~2001-12-26 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26  5:17 severe slowdown with 2.4 series w/heavy disk access Paul Boley
     [not found] ` <01122609375800.01845@manta>
2001-12-25 10:37   ` Paul Boley [this message]
2001-12-26  5:51 ` Idrigal (Eric Rautenkranz)
2001-12-26 14:58 ` Alan Cox
2001-12-25 10:33   ` Paul Boley
2001-12-26 16:46     ` Calin A. Culianu
2001-12-26 17:36     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-12-26 19:25 Guillaume Morin

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=3C2856F4.9BF7B835@home.com \
    --to=pboley@home.com \
    --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