From: Josh Berkus <josh@agliodbs.com>
To: Richard Yen <dba@richyen.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: why does swap not recover?
Date: Mon, 29 Mar 2010 23:18:27 -0700
Message-ID: <4BB197B3.3050306@agliodbs.com> (raw)
In-Reply-To: <04C98397-261D-4A50-99CB-61FA3E4A974B@richyen.com>
References: <04C98397-261D-4A50-99CB-61FA3E4A974B@richyen.com>
On 3/26/10 4:57 PM, Richard Yen wrote:
> I'm planning on lowering the shared_buffers to a more sane value, like 25GB (pgtune recommends this for a Mixed-purpose machine) or less (pgtune recommends 14GB for an OLTP machine). However, before I do this (and possibly resolve the issue), I was hoping to see if anyone would have an explanation for the constant reading from swap, but never writing back.
Postgres does not control how swap is used. This would be an operating
system issue. Leaving aside the distict possibility of a bug in
handling swap (nobody seems to do it well), there's the distinct
possibility that you're actually pinning more memory on the system than
it has (through various processes) and it's wisely shifted some
read-only files to the swap (as opposed to read-write ones). But that's
a fairly handwavy guess.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, dba@richyen.com
Subject: Re: why does swap not recover?
In-Reply-To: <4BB197B3.3050306@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox