Thanks Federico. I think you might be right - pgbouncer does not seem to be maintaining connections to postgresql for
verylong, and as a result when a load spike comes in I suspect there's a fair bit of time and contention in
reestablishingthem. I'm looking there now.
On May 1, 2012, at 5:54 AM, Federico Di Gregorio wrote:
> On 30/04/12 23:29, Russ Neufeld wrote:
>> Hi all,
>>
>> I'm investigating some occasional slowness in our API servers, and I've
>> hit upon some strange behavior that I can't explain. I'm hoping someone
>> on this list can help.
>
> Hi Russ,
>
> you may want to configure PostgreSQL to log connections and queries,
> with execution times. Then cross-check PostgreSQL, Django and pgbouncer
> logs to understand exactly where that 6 seconds are spent. I bet on
> pgbouncer connecting to PostgreSQL (SSL?) but we don't have enough data
> to do a proper analysis here.
>
> federico
>
> --
> Federico Di Gregorio federico.digregorio@dndg.it
> Studio Associato Di Nunzio e Di Gregorio http://dndg.it
> Quis custodiet ipsos custodes? -- Juvenal, Satires, VI, 347
>
> --
> Sent via psycopg mailing list (psycopg@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg
