Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21313 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41921 invoked by uid 1010); 21 Dec 2005 23:08:49 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41906 invoked from network); 21 Dec 2005 23:08:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Dec 2005 23:08:49 -0000 X-Host-Fingerprint: 64.233.184.200 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.200:63803] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id FF/A4-14561-180E9A34 for ; Wed, 21 Dec 2005 18:08:49 -0500 Received: by wproxy.gmail.com with SMTP id i24so246524wra for ; Wed, 21 Dec 2005 15:08:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WZxK3hAs0JT3ZVUT0zrV999Ze/p067D55itTn3LajUBagYYDAo9YSRE1CKRO5se/NryxVTygeuEyjV9kWZOZH8vzZ/X073DeGbdK6Kfevnz0p7aE7ADWrB6qRQdNlH7d8LP4GIcwKZmeXmMz4JzzxxUG+M9w8OEEzDYfwwv6FDc= Received: by 10.54.115.15 with SMTP id n15mr1412316wrc; Wed, 21 Dec 2005 15:08:45 -0800 (PST) Received: by 10.54.77.20 with HTTP; Wed, 21 Dec 2005 15:08:43 -0800 (PST) Message-ID: <4e89b4260512211508q2855e5dckcff7b7430e3629cd@mail.gmail.com> Date: Wed, 21 Dec 2005 18:08:43 -0500 To: steve Cc: Andreas Schiffler , internals@lists.php.net, aschiffler@ferzkopp.net In-Reply-To: <57792e850512211502m79b78efen2e6665ea204cc5b6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A979A4.80307@ic-agency.com> <4e89b4260512211120u47f72a80jf91f0d9e74d1791e@mail.gmail.com> <57792e850512211502m79b78efen2e6665ea204cc5b6@mail.gmail.com> Subject: Re: [PHP-DEV] Change to timeout use From: kingwez@gmail.com (Wez Furlong) The problem isn't the duration of the soap query call, it's how long to wait before giving up on establishing the connection. The connect timeout is completely independent from the soap call duration or the work that it performs. --Wez. On 12/21/05, steve wrote: > > There's not much difference between .25 and 1 second. > > Actually, there is. It depends on the length of time of a typical page > request (and the proportion of the delay to the typical time), and the > hardware setup to handle that. The 4x slowdown can cause a cascade > effect as it might cause more than 4x simultaneous connections on the > target (causing it to slow down, and the problem to keep growing). > That gets amplified by the number of webservers a bit. > > I don't use SOAP in such a way, but it is analogous to MySQL queries, > and having a 1s time for a common query can lead to all sorts of > problems. > > The reason I'm chiming in here is to suggest that if this is looked > at, that it be made universal for all network timeouts. I'm thinking > MySQL in particular, as there could be a class of websites that don't > use custom connection pooling handlers on their webservers to get > around this (useful, for example, if switching to backup servers). > > So maybe fractional seconds for network related timeouts could be a > wishlist item for PHP 6? > > Personally, I wouldn't mind connection pooling too. I like to dream... > > :) >