From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | "Luki Rustianto *EXTERN*" <lukirus(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to find how much postgresql use the memory? |
Date: | 2009-01-22 20:07:00 |
Message-ID: | dcc563d10901221207k42e73af5r30cea1a7b54a6820@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jan 21, 2009 at 10:15 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
>
> Tom Lane suggested in
> http://archives.postgresql.org/pgsql-general/2004-02/msg00471.php
> that it might be better to set shared_buffers "relatively
> small" and let the filesystem cache do the buffering, so that's
> another way you can go. His advice is usually good.
Note that for transactional databases that are too large to fit the
dataset into memory (think a 16Gig machine running a 100G
transactional database) this is very true. The shared_buffers seldom
get reused and you'll get faster throughput with lower shared_buffers.
In testing a 40Gig db on a 32Gig machine, I got the best pgbench
numbers with a shared_buffers setting in the hundreds of megs range.
From | Date | Subject | |
---|---|---|---|
Next Message | David Goodenough | 2009-01-22 20:18:22 | Re: problem converting database to UTF-8 |
Previous Message | Vladimir Konrad | 2009-01-22 20:04:42 | Re: problem converting database to UTF-8 |