From: | Curt Sampson <cjs(at)cynic(dot)net> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Varun Kacholia <varunk(at)cse(dot)iitb(dot)ac(dot)in>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: shared memory |
Date: | 2002-06-22 09:17:41 |
Message-ID: | Pine.NEB.4.43.0206221815470.1091-100000@angelic.cynic.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 17 Jun 2002, Jan Wieck wrote:
> Of course is increasing the number of shared buffers beneficial. It
> usually increases the buffer hit rate in turn, causing lesser IO
> operations and thus increasing the overall performance.
Yes, but the only savings may be in transferring the buffer between
the operating system's buffer cache and the postgres buffer cache.
Remember, the OS is doing buffering as well.
> If you're
> setting up a dedicated DB server, I'd suggest starting with half of the
> physical RAM configured as shared buffers and experimenting from there.
I'd guess that "half" is about the very worst value you could chose.
That will maximize the number of pages that are stored (in duplicate)
in both the OS and postgres buffers, and waste a lot of memory.
cjs
--
Curt Sampson <cjs(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
From | Date | Subject | |
---|---|---|---|
Next Message | Curt Sampson | 2002-06-22 09:23:45 | Re: URGENT: Performance tuning |
Previous Message | Curt Sampson | 2002-06-22 09:10:55 | Re: large database on postgres |