From: "Luke Miller" <millerlu@integraonline.com>
To: <linux-kernel@vger.kernel.org>
Subject: Virtual Memory tuning and Buffers
Date: Fri, 1 Apr 2005 11:08:20 -0800 [thread overview]
Message-ID: <002301c536ee$2b70b450$0a011eac@mimir> (raw)
We have a system that is running SUSE 8 kernel 2.4.21-273. Recently we have
seen some interesting behavior with the virtual memory system. When buffer
memory gets low (below 10 MB) the system re-allocates memory causes buffer
memory to go up to around 500 MB. The re-allocation can take up to 30
minutes. This system is an NFS server and during the re-allocation all the
NFSd's go to IO wait and the NFS clients gets delays trying to access files
on the NFS volumes. I have generated some graphs that show this pretty
clearly, they are here:
http://www.integraonline.com/~millerlu/memory/
What I am trying to figure out is what is causing this memory allocations
and what can be done to tune them so it doesn't impact our production
applications when it happens.
Due to a clustering and file system product, Polyserve, we are unable to
upgrade to the 2.6 kernel at this time.
Any help would be appreciated.
Thanks,
Luke
reply other threads:[~2005-04-01 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002301c536ee$2b70b450$0a011eac@mimir' \
--to=millerlu@integraonline.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
Powered by JetHome