public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Alex Buell <alex.buell@munted.org.uk>,
	linux-kernel@vger.kernel.org, riel@redhat.com, arjanv@redhat.com
Subject: Re: inode_cache / dentry_cache not being reclaimed aggressively enough  on low-memory PCs
Date: Mon, 5 Jan 2004 10:47:41 -0800	[thread overview]
Message-ID: <20040105184741.GA1882@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58L.0401051531040.5618@logos.cnet>

On Mon, Jan 05, 2004 at 03:32:57PM -0200, Marcelo Tosatti wrote:
> 
> 
> On Sat, 3 Jan 2004, Mike Fedyk wrote:
> > Also, if there are any improvements considered for the 2.4 VM, it should be
> > on top of the -aa series.  That's where the latest updates are, and it
> > doesn't make sence to work from a base that already has seperate
> > improvements available.
> 
> The fix in -aa seems to reclaim inodes very aggressively. The 2.4 RH tree
> seems to contain a better version. Need to look into that.

http://www.matchmail.com/stats/lrrd/matchmail.com/fileserver.matchmail.com-memory.html

Comparing[1] week 51 (2.4.23-rc5), and week 01 (2.4.23-aa1) would show that the
slab cache can grow larger for the same workload in -aa right now.

I have a backup that runs every day at 4-6am that is somewhat memory
intensive since it uses smbfs, (that's notorious for its bad memory usage
patterns) and it doesn't shrink the slab at all.  The only thing that
affected slab size was closing one of my mutt instances that was running on
a maildir folder with 28k messages in it on tuesday of week 01.



http://www.matchmail.com/stats/lrrd/matchmail.com/fileserver.matchmail.com-swap.html

2.4.23-aa may or may not have problems with inode/dentry reclaim (I haven't
checked other workloads), but it sure improves the amount of swap I/O
performed.



Here's the top slab users right now:

inode_cache       456388 457304    512 57163 57163    1 : 534792 4012606
132385 68961    0 :  124

dentry_cache      626116 641116    136 22897 22897    1 : 731108 7905948
51318 27096    0 :  252  12

buffer_head       127878 132732    108 3684 3687    1 : 163476 29891760
62063 58376    0 :  252  126

size-64           137960 141934     72 2678 2678    1 : 152534 2392141  3263
585    0 :  252  126 :

vm_area_struct      5586   6600     76  124  132    1 :   8650 17144108
1294 1162    0 :  252  126

blkdev_requests     4096   4120     96  103  103    1 :   4640    5018
11613    0 :  252  126 :

size-4096             98     98   4096   98   98    1 :    827  264784
173433 173335    0 :   60   3



  reply	other threads:[~2004-01-05 18:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-03 11:35 inode_cache / dentry_cache not being reclaimed aggressively enough on low-memory PCs Alex Buell
2004-01-03 16:30 ` John Lash
2004-01-03 18:27   ` Alex Buell
2004-01-03 22:24     ` Mike Fedyk
2004-01-03 22:55   ` Andrew Morton
2004-01-04  0:15     ` Alex Buell
2004-01-04  3:05       ` Andrew Morton
2004-01-04  7:23         ` Mike Fedyk
2004-01-05 17:32           ` Marcelo Tosatti
2004-01-05 18:47             ` Mike Fedyk [this message]
2004-01-09 20:49             ` Rik van Riel
2004-01-04  5:31     ` John Lash

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=20040105184741.GA1882@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=alex.buell@munted.org.uk \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=riel@redhat.com \
    /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