From: mike <mike503@gmail.com>
To: Chris Snook <csnook@redhat.com>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>, linux-mm@kvack.org
Subject: Re: Drop caches - is this safe behavior?
Date: Thu, 23 Aug 2007 22:27:36 -0700 [thread overview]
Message-ID: <bd9320b30708232227v1b297a42pd9b20e04aef758d7@mail.gmail.com> (raw)
In-Reply-To: <46CE69DE.9040807@redhat.com>
On 8/23/07, Chris Snook <csnook@redhat.com> wrote:
> Mike --
>
> Try Dave's suggestion to increase vm.vfs_cache_pressure. drop_pages
> should never be needed, regardless of which caches you're dropping.
>
> -- Chris
>
thanks all. i will try it on one of the machines and see how it performs.
this is an opteron 1.8ghz (amd64), ubuntu, latest stable linux kernel,
3 gigs of ram (just FYI) - SATA disk.
i thought i'd do it every 5 minutes not because of a horrible memory
leak that fast, but figured "why not just free up all RAM as often as
possible"
when you said "sar" are you talking about this:
atsar - system activity reporter
Description: system activity reporter
Monitor system resources such as CPU, network, memory & disk I/O, and
record data for later analysis
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-24 5:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bd9320b30708231645x3c6524efi55dd2cf7b1a9ba51@mail.gmail.com>
2007-08-24 0:07 ` mike
2007-08-24 1:36 ` Chris Snook
2007-08-24 4:35 ` mike
2007-08-24 5:14 ` Chris Snook
2007-08-24 4:47 ` Dave Kleikamp
2007-08-24 5:17 ` Chris Snook
2007-08-24 5:27 ` mike [this message]
2007-08-24 5:52 ` Chris Snook
2007-08-24 7:12 ` mike
2007-08-24 19:30 ` Chris Snook
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=bd9320b30708232227v1b297a42pd9b20e04aef758d7@mail.gmail.com \
--to=mike503@gmail.com \
--cc=csnook@redhat.com \
--cc=linux-mm@kvack.org \
--cc=shaggy@linux.vnet.ibm.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