Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 17BBE632433 for ; Tue, 5 Jan 2010 23:28:50 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 49327-03 for ; Wed, 6 Jan 2010 03:28:30 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-px0-f194.google.com (mail-px0-f194.google.com [209.85.216.194]) by mail.postgresql.org (Postfix) with ESMTP id 2CCC6632CB4 for ; Tue, 5 Jan 2010 23:28:38 -0400 (AST) Received: by pxi32 with SMTP id 32so11590457pxi.15 for ; Tue, 05 Jan 2010 19:28:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=W6Xkt39kRy3Zj6TCaOq72g3EtsIfG8KzlPI5OxgaSZQ=; b=nMRYBcS8UD6HF8KW5mLyO0U0RiKqz3hxlO7M90QWaZ4hFTXSypdQVfrdWL074+fDkR mI8RAdlhVBTDcnmgu7TVzDL3ZYfd8h/xDgfVNeCTZXLWjkoIzvslPLNoXAx396e3T7vH yWKglElk1/GfBqHyGoxMGkEp3eqcZGYq3Ul7s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=xrr+34+GFtgEIc052IugeXOv47wFPH89UTCclVdtsrf5bKH2+Ev7P+MDUBD71nvOxb CtgAuqOEGgv3kLG0QLnTtObBjvkIoEU8ztZGWVSfbUyk7esUDcNCjhys65T/DGUIzXpG 3WcgIVapFqww3iFqlPabbBujKg5E247k6FtYY= MIME-Version: 1.0 Received: by 10.114.186.15 with SMTP id j15mr1653515waf.52.1262748517120; Tue, 05 Jan 2010 19:28:37 -0800 (PST) In-Reply-To: References: From: Dmitri Girski Date: Wed, 6 Jan 2010 14:28:17 +1100 X-Google-Sender-Auth: 16c5ba5a19c296b9 Message-ID: Subject: Re: pg_connect takes 3.0 seconds To: Scott Carey Cc: "pgsql-performance@postgresql.org" Content-Type: multipart/alternative; boundary=0016e64ca56acdba20047c768c42 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.59 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FH_DATE_PAST_20XX=3.188, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201001/53 X-Sequence-Number: 36933 --0016e64ca56acdba20047c768c42 Content-Type: text/plain; charset=ISO-8859-1 Hi Scott, Thank you pointers, I've spoken to the network guy, he will help to monitor connections on the firewall. On the other hand, if I use ip addresses this should not attract any possible issues with DNS, right? Thanks! Dmitri. On Wed, Jan 6, 2010 at 9:32 AM, Scott Carey wrote: > 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" 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. > > > > > > -- @Gmail --0016e64ca56acdba20047c768c42 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Scott,

Thank yo= u pointers, I've spoken to the network guy, he will help to monitor con= nections on the firewall.=A0
On the other hand, if I use ip addresses this = should not attract any possible issues with DNS, right?

Thanks!

Dmitri.

On Wed, Jan 6, 2010 at 9:32 AM, Scott Carey <scott@richrelevance.com> = wrote:
Delays that are almost exactly 3 seconds ov= er 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 con= fig.
>
> The web application server which runs Apache 1.3/PHP2.9 =A0has an inte= rmittent
> problem:
> pg_connect takes exactly 3.0 seconds. The usual connection time is 0.0= 045.
> The long request happens at approximate rate 1:100.
>
> I turned on logs on postgres server side, and there is nothing=A0suspi= cious=A0for
> me there. When a connection request comes, it is being served without = any
> delay.=A0
>
> Could anyone point me to the direction in which I should investigate t= his
> problem further?
> Thank you in advance!
>
>
> PS The hardware is: Dell=A0SC1435/4Gb/2x2.0GHz/Gentoo Linux.
> The database & web servers are in the 2 local subnets.=A0
>
>
> Dmitri.
>
>




--
@Gmail
--0016e64ca56acdba20047c768c42--