From: Alan Stange <stange@rentec.com>
To: Kevin Schroeder <kschroeder@mirageworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Swapping on Solaris
Date: Wed, 19 Jan 2005 10:30:33 -0500
Message-ID: <41EE7D19.4060503@rentec.com> (raw)
In-Reply-To: <00d601c4fe33$89682eb0$0200a8c0@WORKSTATION>
References: <042a01c4fdaf$fbb3b860$0200a8c0@WORKSTATION>
<41EE0F05.9080901@coretech.co.nz>
<41EE65FC.2000909@rentec.com>
<00d601c4fe33$89682eb0$0200a8c0@WORKSTATION>
Kevin Schroeder wrote:
> I suspect that the memory is being used to cache files as well since
> the email boxes are using unix mailboxes, for the time being. With
> people checking their email sometimes once per minute I can see why
> Solaris would want to cache those files. Perhaps my question would be
> more appropriate to a Solaris mailing list since what I really want to
> do is get Solaris to simply allow PostgreSQL to use more RAM and
> reduce the amount of RAM used for file caching. I would have thought
> that Solaris gives some deference to a running application that's
> being swapped than for a file cache.
>
> Is there any way to set custom parameters on Solaris' file-caching
> behavior to allow PostgreSQL to use more physical RAM?
Your explanation doesn't sound quite correct. If postgresql malloc()'s
some memory and uses it, the file cache will be reduced in size and the
memory given to postgresql. But if postgresql doesn't ask for or use
the memory, then solaris is going to use it for something else. There's
nothing in Solaris that doesn't "allow" postgresql to use more RAM.
-- Alan
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: stange@rentec.com, kschroeder@mirageworks.com
Subject: Re: Swapping on Solaris
In-Reply-To: <41EE7D19.4060503@rentec.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