From: Scott Carey <scott@richrelevance.com>
To: Dmitri Girski <mitek17@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: pg_connect takes 3.0 seconds
Date: Tue, 5 Jan 2010 14:32:12 -0800
Message-ID: <C768FDEC.1DDB4%scott@richrelevance.com> (raw)
In-Reply-To: <daed64561001041812s602a3098l686f630d6448835f@mail.gmail.com>
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@gmail.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.
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott@richrelevance.com, mitek17@gmail.com
Subject: Re: pg_connect takes 3.0 seconds
In-Reply-To: <C768FDEC.1DDB4%scott@richrelevance.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox