| From: | "Tomas Vondra" <tv(at)fuzzy(dot)cz> |
|---|---|
| To: | "Ogden" <lists(at)darkstatic(dot)com> |
| Cc: | "Andy Colson" <andy(at)squeakycode(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Tuning Tips for a new Server |
| Date: | 2011-08-17 15:08:31 |
| Message-ID: | fa91e97f5c67b2d07729a618ccca4bd7.squirrel@sq.gransy.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 17 Srpen 2011, 16:28, Ogden wrote:
> I was wondering what the best parameters would be with my new setup. The
> work_mem obviously will increase as will everything else as it's a 64Gb
> machine as opposed to a 16Gb machine. The configuration I posted was for
> a 16Gb machine but this new one is 64Gb. I needed help in how to jump
> these numbers up.
Well, that really depends on how you come to the current work_mem settings.
If you've decided that with this amount of work_mem the queries run fine
and higher values don't give you better performance (because the amount of
data that needs to be sorted / hashed) fits into the work_mem, then don't
increase it.
But if you've just set it so that the memory is not exhausted, increasing
it may actually help you.
What I think you should review is the amount of shared buffers,
checkpoints and page cache settings (see this for example
http://notemagnet.blogspot.com/2008/08/linux-write-cache-mystery.html)
Tomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2011-08-17 15:27:09 | Re: How to see memory usage using explain analyze ? |
| Previous Message | Tomas Vondra | 2011-08-17 14:44:39 | Re: Tuning Tips for a new Server |