From: | Scott Carey <scott(at)richrelevance(dot)com> |
---|---|
To: | Dmitri Girski <mitek17(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: pg_connect takes 3.0 seconds |
Date: | 2010-01-05 22:32:12 |
Message-ID: | C768FDEC.1DDB4%scott@richrelevance.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Delays that are almost exactly 3 seconds over a network are almost always
some sort of network configuration issue.
Inside a datacenter, mis-configured load balancers or routers can cause low
level network issues that result in intermittent network delays of exactly 3
seconds (a loop in a routing network?).
DNS timeouts are often 3 seconds.
Not sure if any of the above is it, but this sounds like a network
configuration problem to me.
On 1/4/10 6:12 PM, "Dmitri Girski" <mitek17(at)gmail(dot)com> wrote:
> Hi everybody,
>
> I am running a PostgreSQL server 8.3.5 with a pretty much standard config.
>
> The web application server which runs Apache 1.3/PHP2.9 has an intermittent
> problem:
> pg_connect takes exactly 3.0 seconds. The usual connection time is 0.0045.
> The long request happens at approximate rate 1:100.
>
> I turned on logs on postgres server side, and there is nothing suspicious for
> me there. When a connection request comes, it is being served without any
> delay.
>
> Could anyone point me to the direction in which I should investigate this
> problem further?
> Thank you in advance!
>
>
> PS The hardware is: Dell SC1435/4Gb/2x2.0GHz/Gentoo Linux.
> The database & web servers are in the 2 local subnets.
>
>
> Dmitri.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Carey | 2010-01-06 01:04:32 | Re: DB is slow until DB is reloaded |
Previous Message | Brian Cox | 2010-01-05 21:33:08 | Re: query looping? |