Message-ID: <47E76087.3050901@postnewspapers.com.au>
Date: Mon, 24 Mar 2008 17:04:23 +0900
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: firerox@centrum.cz
Cc: pgsql-performance@postgresql.org
Subject: Re: slow pg_connect()
References: <200803240840.8128@centrum.cz>
	<47E75F18.9060206@postnewspapers.com.au>
In-Reply-To: <47E75F18.9060206@postnewspapers.com.au>
Content-Type: text/plain; charset=windows-1250; format=flowed
Content-Transfer-Encoding: 7bit

Craig Ringer wrote:
> firerox@centrum.cz wrote:
>> It takes more then 0.05s :(
>>
>> Only this function reduce server speed max to 20request per second.
>>   
> If you need that sort of frequent database access, you might want to 
> look into:
>
> - Doing more work in each connection and reducing the number of 
> connections required;
> - Using multiple connections in parallel;
> - Pooling connections so you don't need to create a new one for every 
> job;
> - Using a more efficient database connector and/or language;
> - Dispatching requests to a persistent database access provider that's 
> always connected
>
Oh, I missed:

Use a UNIX domain socket rather than a TCP/IP local socket. Database 
interfaces that support UNIX sockets (like psycopg) will normally do 
this if you omit the host argument entirely.

--
Craig Ringer