Re: bgwriter, checkpoints, curious (seeing delays) - Mailing list pgsql-performance

From Tory M Blue
Subject Re: bgwriter, checkpoints, curious (seeing delays)
Date
Msg-id 8a547c841002261052r3bff71f2v6759859abce72710@mail.gmail.com
Whole thread Raw
In response to Re: bgwriter, checkpoints, curious (seeing delays)  (Devrim GÜNDÜZ <devrim@gunduz.org>)
Responses Re: bgwriter, checkpoints, curious (seeing delays)
Re: bgwriter, checkpoints, curious (seeing delays)
List pgsql-performance
2010/2/25 Devrim GÜNDÜZ <devrim@gunduz.org>:
> On Thu, 2010-02-25 at 22:12 -0800, Tory M Blue wrote:
>> shared_buffers = 1500MB
>
> Some people tend to increase this to 2.2GB(32-bit) or 4-6 GB (64 bit),
> if needed. Please note that more shared_buffers will lead to more
> pressure on bgwriter, but it also has lots of benefits, too.
>
>> work_mem = 100MB
>
> This is too much. Since you have 300 connections, you will probably swap
> because of this setting, since each connection may use this much
> work_mem. The rule of the thumb is to set this to a lower general value
> (say, 1-2 MB), and set it per-query when needed.

I'm slightly confused. Most things I've read, including running
pg_tune for grins puts this around 100MB, 98MB for pgtune.  1-2MB just
seems really low to me. And Ignore the 300 connections, thats an upper
limit, I usually run a max of 40-45 but usually around 20 connections
per sec.


Also is there a way to log if there are any deadlocks happening (I'm
not seeing them in logs)
deadlock_timeout = 5s

Tory

pgsql-performance by date:

Previous
From: Ben Chobot
Date:
Subject: Re: bgwriter, checkpoints, curious (seeing delays)
Next
From: Tory M Blue
Date:
Subject: Re: bgwriter, checkpoints, curious (seeing delays)