From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Cosimo Streppone <cosimo(at)streppone(dot)it>, Richard Huxton <dev(at)archonet(dot)com>, Postgresql Performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Context switch storm |
Date: | 2006-11-14 16:50:22 |
Message-ID: | 20061114165022.GS90133@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Nov 14, 2006 at 09:17:08AM -0500, Merlin Moncure wrote:
> On 11/14/06, Cosimo Streppone <cosimo(at)streppone(dot)it> wrote:
> >I must say I lowered "shared_buffers" to 8192, as it was before.
> >I tried raising it to 16384, but I can't seem to find a relationship
> >between shared_buffers and performance level for this server.
>
> My findings are pretty much the same here. I don't see any link
> between shared buffers and performance. I'm still looking for hard
> evidence to rebut this point. Lower shared buffers leaves more
> memory for what really matters, which is sorting.
It depends on your workload. If you're really sort-heavy, then having
memory available for that will be hard to beat. Otherwise, having a
large shared_buffers setting can really help cut down on switching back
and forth between the kernel and PostgreSQL.
BTW, shared_buffers of 16384 is pretty low by today's standards, so that
could be why you're not seeing much difference between that and 8192.
Try upping it to 1/4 - 1/2 of memory and see if that changes things.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Bucky Jordan | 2006-11-14 17:53:16 | Re: Context switch storm |
Previous Message | Merlin Moncure | 2006-11-14 14:17:08 | Re: Context switch storm |