| From: | Russ Neufeld <russn(at)nasuni(dot)com> |
|---|---|
| To: | Federico Di Gregorio <fog(at)dndg(dot)it> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: Strange slowness |
| Date: | 2012-05-01 21:30:59 |
| Message-ID: | 68683144-6732-4E94-807E-23BE43EC0977@nasuni.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
Thanks Federico. I think you might be right - pgbouncer does not seem to be maintaining connections to postgresql for very long, and as a result when a load spike comes in I suspect there's a fair bit of time and contention in reestablishing them. 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(dot)digregorio(at)dndg(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/psycopg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russ Neufeld | 2012-05-01 21:31:36 | Re: Strange slowness |
| Previous Message | Federico Di Gregorio | 2012-05-01 09:54:20 | Re: Strange slowness |