From: Rik van Riel <riel@redhat.com>
To: "Kevin Burton" <burton@tailrank.com>
Cc: "FD Cami" <francois.cami@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Ability to limit or disable page caching?
Date: Mon, 5 May 2008 16:44:46 -0400 [thread overview]
Message-ID: <20080505164446.2ec9a543@cuia.bos.redhat.com> (raw)
In-Reply-To: <30c6373b0805051242o2f38f0a3v62bd43f4fa01559e@mail.gmail.com>
On Mon, 5 May 2008 12:42:31 -0700
"Kevin Burton" <burton@tailrank.com> wrote:
> What's happening is that the kernel is deciding to swap out some
> memory to disk in the (false) belief that it can free some up for
> cache.
>
> The problem is my database is already using its own cache so these are
> conflicting philosophies here which make Linux perform in a
> pathological way..
One of the problems is that the process pages (anonymous memory) and
page cache pages live on the same LRU, so the kernel cannot always
easily find the page cache pages when it is trying to evict something.
Once that is fixed, and replacement is biased towards evicting page
cache pages, the system may do the right thing by itself.
I realize that this is no quick fix for your issue, but I am working
on a split LRU patch series to make sure Linux does the right thing in
the future.
You can find the latest patch at http://people.redhat.com/riel/splitvm/
and info on the design at http://linux-mm.org/PageReplacementDesign
> What I want to do is either disable the page cache entirely or just
> tell the OS to cache at max 10% of the available memory.
I have no such tunable in my code (yet), because I would like the
kernel to do the right thing automatically. I will post a 2.6.25 based
kernel RPM for Fedora 9 soon with the split LRU patch series applied.
If you feel like testing/breaking it, I would be interested to see if
it does indeed do the right thing for your workload or if it needs more
tuning.
--
All Rights Reversed
next prev parent reply other threads:[~2008-05-05 20:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 7:12 Ability to limit or disable page caching? Kevin Burton
2008-05-05 11:16 ` FD Cami
2008-05-05 18:34 ` Kevin Burton
2008-05-05 19:28 ` FD Cami
2008-05-05 19:42 ` Kevin Burton
2008-05-05 20:10 ` Andi Kleen
2008-05-05 20:28 ` Kevin Burton
2008-05-05 20:31 ` Kevin Burton
2008-05-05 20:40 ` Kevin Burton
2008-05-06 0:23 ` Andi Kleen
2008-05-06 0:30 ` Kevin Burton
2008-05-05 21:24 ` Bernd Eckenfels
2008-05-05 20:44 ` Rik van Riel [this message]
2008-05-05 21:00 ` Kevin Burton
2008-05-05 22:08 ` Rik van Riel
2008-05-05 22:15 ` Kevin Burton
2008-05-08 2:08 ` split LRU kernel RPM Rik van Riel
2008-05-05 21:03 ` Ability to limit or disable page caching? Chris Friesen
2008-05-05 21:32 ` Kevin Burton
2008-05-05 22:06 ` Rik van Riel
2008-05-06 11:02 ` Tomasz Kłoczko
2008-05-05 19:33 ` Kevin Burton
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=20080505164446.2ec9a543@cuia.bos.redhat.com \
--to=riel@redhat.com \
--cc=burton@tailrank.com \
--cc=francois.cami@free.fr \
--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