From: | Dmitri Girski <mitek17(at)gmail(dot)com> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pg_connect takes 3.0 seconds |
Date: | 2010-01-06 03:25:00 |
Message-ID: | daed64561001051925k26682e50ue1792e7032a75bd5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Andy,
I tried 2 connections strings:
- server name (DB1), which is listed in all machines hosts files.
- ip address.
There is no difference in both methods, still I have 5-7 pg_connects which
last around 3 seconds.
Cheers,
Dmitri.
On Wed, Jan 6, 2010 at 2:03 AM, Andy Colson <andy(at)squeakycode(dot)net> wrote:
> On 1/4/2010 8:12 PM, Dmitri Girski 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.
>>
>>
> How do you have the connect string? With an IP or a name? Maybe its a DNS
> lookup timeout? You could switch to IP or drop the name in the hosts file
> and see if that makes a difference.
>
> -Andy
>
--
@Gmail
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitri Girski | 2010-01-06 03:28:17 | Re: pg_connect takes 3.0 seconds |
Previous Message | Robert Haas | 2010-01-06 01:34:01 | Re: query looping? |