From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | jam3 <jamorton3(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Would my postgresql 8.4.12 profit from doubling RAM? |
Date: | 2012-09-05 21:10:14 |
Message-ID: | CAOR=d=3YuamqWL5b56b424E7yYE3QS2n4uosOhqFwu8AXXf+5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Sep 5, 2012 at 2:16 PM, jam3 <jamorton3(at)gmail(dot)com> wrote:
> Here is a bash script I wrote to print out mem config ffrom postgresconf.sql
> and os (centos 5.5 in this case). According to Gregory Smith in Postgresql
> 9.0 shared buffers should be appx 25-40% of avail Physical RAM. Also
> considerPostgres uses the OS Buffer as it access the physical data and log
> files and while doing so has the potential to double buffer blocks.
>
> WorkMEM is suggested at 5% but if you do alot of CLUSTER/ANALYZE/VACUUM you
> will want to up this, I usually round off to the highest power of 2 is 5% is
> 328mb i'll set it to 512.
I think you mean maintenance_work_mem here, as regular vacuum or
analyze don't use work_mem.
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2012-09-05 21:27:44 | Re: Re: Where is the char and varchar length in pg_catalog for function input variables |
Previous Message | David Johnston | 2012-09-05 21:05:07 | Re: Re: Where is the char and varchar length in pg_catalog for function input variables |