From: John A Meinel <john@arbash-meinel.com>
To: Neil Conway <neilc@samurai.com>
Cc: Tom Arthurs <tarthurs@jobflash.com>
Cc: Donald Courtney <Donald.Courtney@Sun.COM>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgresql on an AMD64 machine
Date: Tue, 07 Jun 2005 19:44:18 -0500
Message-ID: <42A63F62.40007@arbash-meinel.com> (raw)
In-Reply-To: <42A639C3.40606@samurai.com>
References: <1118080420.1644.23.camel@penguin1>
<b918cf3d05060613593a73a18a@mail.gmail.com>
<42A5F7B6.20502@sun.com>
<42A5FB70.8090807@jobflash.com>
<42A6014C.30108@sun.com>
<42A605E8.8040607@jobflash.com>
<42A639C3.40606@samurai.com>
Neil Conway wrote:
> Tom Arthurs wrote:
>
>> Yes, shared buffers in postgres are not used for caching
>
>
> Shared buffers in Postgres _are_ used for caching, they just form a
> secondary cache on top of the kernel's IO cache. Postgres does IO
> through the filesystem, which is then cached by the kernel. Increasing
> shared_buffers means that less memory is available for the kernel to
> cache IO -- increasing shared_buffers has been shown to be a net
> performance loss beyond a certain point. Still, there is value in
> shared_buffers as it means we can avoid a read() system call for hot
> pages. We can also do better buffer replacement in the PG shared buffer
> than the kernel can do (e.g. treating IO caused by VACUUM specially).
>
As I recall, one of the performance problems with a large shared_buffers
is that there are some commands which require looking at *all* of the
shared buffer space. So the larger it gets, the longer those functions take.
>> My biggest challenge with solaris/sparc is trying to reduce context
>> switching.
>
>
> It would be interesting to see if this is improved with current sources,
> as Tom's bufmgr rewrite should have hopefully have reduced this problem.
>
These might be what was fixed with Tom's rewrite. I don't really know.
John
=:->
> -Neil
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
Attachments:
signature.asc (application/pgp-signature, 250B) download
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: john@arbash-meinel.com, neilc@samurai.com, tarthurs@jobflash.com, Donald.Courtney@Sun.COM
Subject: Re: Postgresql on an AMD64 machine
In-Reply-To: <42A63F62.40007@arbash-meinel.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