Re: Postgresql on an AMD64 machine

From: Tom Arthurs <tarthurs(at)jobflash(dot)com>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Donald Courtney <Donald(dot)Courtney(at)Sun(dot)COM>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgresql on an AMD64 machine
Date: 2005-06-08 16:43:51
Message-ID: 42A72047.6030304@jobflash.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I just puhsd 8.0.3 to production on Sunday, and haven't had a time to
really monitor it under load, so I can't tell if it's helped the context
switch problem yet or not.

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).
>
>> 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.
>
> -Neil
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Joshua D. Drake 2005-06-08 16:48:12 Re: Help specifying new web server/database machine
Previous Message Bjoern Metzdorf 2005-06-08 16:41:01 Re: Help specifying new web server/database machine