Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34598
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain dealnews.com designates 129.41.69.185 as permitted sender)
Message-ID: <4782BBC8.1070301@dealnews.com>
Date: Mon, 07 Jan 2008 17:54:48 -0600
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: mysql.connect_timeout default
From: brianm@dealnews.com (Brian Moon)

I would like to propose we set this default value to something more 
appropriate for a web app.  It is currently 60 seconds.  That is a 
really long time for a web page to wait to find a mysql server, IMO. 
And in the spirit of PHP being web first, I think it should be shorter.

The place where this is an issue is when the server is down completely. 
  This bit me in the butt today.  If the server is up, but mysqld is 
not, PHP will disconnect immediately. But if there is no server 
answering on that IP address, PHP will wait `mysql.connection_timeout` 
seconds before telling you it could not connect to the server.

FWIW, the default for MySQL server is 10 seconds (increased from 5 last 
fall) for a connection timeout.

I personally like 5 seconds for the default unless someone knows a 
reason this is a bad idea.  Is there some other internal trigger to the 
connection that could cause this to be hit at 5 seconds?

Other thoughts?

-- 

Brian Moon
Senior Developer
------------------------------
When you care enough to spend the very least.
http://dealnews.com/