Re: Postgresql on an AMD64 machine

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Arthurs <tarthurs(at)jobflash(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 00:20:19
Message-ID: 42A639C3.40606@samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message John A Meinel 2005-06-08 00:44:18 Re: Postgresql on an AMD64 machine
Previous Message Simon Riggs 2005-06-07 22:21:48 Re: slow growing table