On Wed, 20 May 2009, Kobby Dapaah wrote:
> shared_buffers = 2048MB
> effective_cache_size = 5400MB
You should consider seriously increasing effective_cache_size. You might
also double or quadruple shared_buffers from 2GB, but going much higher
may not buy you much--most people seem to find diminishing returns
increasing that beyond the 10GB range.
> bgwriter_delay = 10ms
> bgwriter_lru_maxpages = 0
I found that bg_writer_delay doesn't really work so well when set to this
small. It doesn't actually matter right now though, because you're
turning the background writer off by setting brwriter_lru_maxpages=0.
Just wanted to point this out because if you increase that later it may
pop up as a concern, small values for the delay make it more likely you'll
need to increase the multiplier to a higher value for background writing
to work well.
Robert's message already mentions the other things you should consider,
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
In response to
pgsql-performance by date
|Next:||From: Daniel Ferreira||Date: 2009-05-21 11:42:46|
|Subject: query planner uses sequencial scan instead of index scan|
|Previous:||From: Robert Haas||Date: 2009-05-21 03:09:52|
|Subject: Re: postgresql.conf suggestions?|