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: Fri, 24 Aug 2007 00:12:15 -0700 [thread overview]
Message-ID: <bd9320b30708240012m6d44ea6wb346d0b4db76e00d@mail.gmail.com> (raw)
In-Reply-To: <46CE7211.2010708@redhat.com>
On 8/23/07, Chris Snook <csnook@redhat.com> wrote:
> I think the caches you had in mind were the ones that would be dropped
> by echoing '1' into /proc/sys/vm/drop_caches, not the ones that would be
> dropped by echoing '2' into it. If you were dropping pagecache every
> five minutes, it would kill your performance as you described. As for
> the question of safety, '3' should also be safe, but terrible for
> performance, as it does all the harm of '1', plus some.
actually right now the performance seems to be good - using "2"
i'm willing to try "1" as well, as well as try the cache pressure one.
i don't really know what caches i am clearing, but it seems that i get
bottlenecked by something. restarting my webserver/php engines usually
clears it up, so it seems like it is a buildup of something - and it
always seems to be when memory is tight...
> I'm not familiar with the "atsar" implementation, but it appears to be
> an alternate implementation of the same thing. It's an excellent tool
> for long-term workload profiling.
actually, this might be a better method - is there any way to view the
contents of the cache? or figure out what exactly is sitting in
there/why my machine thinks it needs to cache 2 gigs of files so
quickly?
--
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 7:12 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
2007-08-24 5:52 ` Chris Snook
2007-08-24 7:12 ` mike [this message]
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=bd9320b30708240012m6d44ea6wb346d0b4db76e00d@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