From: Jakob Oestergaard <jakob@unthought.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 - large inode_cache
Date: Thu, 26 Feb 2004 14:53:33 +0100 [thread overview]
Message-ID: <20040226135333.GQ29776@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0402261109190.5003@logos.cnet>
On Thu, Feb 26, 2004 at 11:23:46AM -0300, Marcelo Tosatti wrote:
...
> > Will a heap of busy knfsd processes doing reads or writes exert
> > pressure? Or is it only local userspace that can pressurize the VM (by
> > either anonymously backed memory or file I/O).
>
> Any allocator will cause VM pressure.
And I suppose that a busy knfsd qualifies as an "allocator" :)
...
> > Any enlightenment or suggestions are greatly appreciated :)
>
> What you can try is to increase the VM tunable vm_vfs_scan_ratio. This is
> the proportion of VFS unused d/i caches that will try to be in one VM
> freeing pass. The default is 6. Try 4 or 3.
>
> /proc/sys/vm/vm_vfs_scan_ratio
Done! Set to 3 now - I will let the box run with this setting until
tomorrow, and report back how things look.
> You can also play with
>
> /proc/sys/vm/vm_cache_scan_ratio (which is the percentage of cache which
> will be scanned in one go).
I'm leaving this one be for now (one variable at a time). But let's see
what tomorrow brings.
Judging from the code, it seems that it's the vm_vfs_scan_ratio that
directly affects the icache/dcache and dquot - but I'm sure that there
are subtle interactions far beyond what I can possibly hope to
comprehend ;)
Thanks a lot for your suggestions Marcelo!
/ jakob
next prev parent reply other threads:[~2004-02-26 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 1:33 2.4.25 - large inode_cache Jakob Oestergaard
2004-02-26 11:19 ` Christian Leber
2004-02-26 13:08 ` Marcelo Tosatti
2004-02-26 13:03 ` Jakob Oestergaard
2004-02-26 14:23 ` Marcelo Tosatti
2004-02-26 13:53 ` Jakob Oestergaard [this message]
2004-02-26 17:43 ` Andreas Dilger
2004-02-26 20:43 ` Marcelo Tosatti
2004-02-27 12:27 ` Jakob Oestergaard
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=20040226135333.GQ29776@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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