Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65381 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55533 invoked from network); 29 Jan 2013 13:33:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jan 2013 13:33:56 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.128.174 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.128.174 mail-ve0-f174.google.com Received: from [209.85.128.174] ([209.85.128.174:43674] helo=mail-ve0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E5/99-10721-3CFC7015 for ; Tue, 29 Jan 2013 08:33:55 -0500 Received: by mail-ve0-f174.google.com with SMTP id c13so264048vea.19 for ; Tue, 29 Jan 2013 05:33:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding:x-gm-message-state; bh=3qvy0ALAVAmPeU6DUgRZLf4sZYHmgMNRYsgFbGRUdXQ=; b=Qc6aw0zFeFyKnucAwB0H/13IY7vyX8D9MykwX5IFwBJdykXBfthD3zYkbY3xt+LOh4 80YDZfWCG8mc1sh1lw04SVnpxAvPjs31kip5hU4JOZzseysgXz9e3CgQt6KAMeGyRDhl kjU4e1cEqtDKHAlhgGwdyZ/nvkz1Mqy+ENwSLiBq6bcSbSUrjxHnVvI7D9XVPCN/cjB8 OG7spsOW7TYJT0bH01udutT/CjrjqUBvK98zFiJdeaMLVECzEqhgywyA5MMH9Dslm4Tu Ro2w56epL6h6not6Hz+Q0eDiubtb9QIbZGrdtL2ByPwIOlfvD6dCjIsQAHdmvlfzTX5c 2UOA== X-Received: by 10.220.149.82 with SMTP id s18mr984226vcv.14.1359466432783; Tue, 29 Jan 2013 05:33:52 -0800 (PST) Received: from [192.168.200.148] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPS id m10sm8339881vei.10.2013.01.29.05.33.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Jan 2013 05:33:51 -0800 (PST) Message-ID: <5107CFBD.80606@lerdorf.com> Date: Tue, 29 Jan 2013 05:33:49 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Pierre Joye CC: PHP internals References: <1359459921.3916.105.camel@guybrush> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQm0BMdvcVyYrII9TpnyVnZHvgTpuqbPhfGhRYRm035vQXKGIOt6IB83MkIdlKSnPjfMZ3Mf Subject: Re: [PHP-DEV] ZTS - why are you using it? From: rasmus@lerdorf.com (Rasmus Lerdorf) On 01/29/2013 05:18 AM, Pierre Joye wrote: > As far as I remember, we already do that for a couple of web servers. > And in the long run, I will rather tell not to use FastCGI for > dedicated hosting and the likes. That being said, I also met many ISPs > which are not happy with the all-fastcgi, memory usageand performance > were the issues (have to read my backlog for other details :). Those ISPs are probably stuck in old fastcgi-land and haven't figured out FPM's ondemand pooling. If you idle out the ondemand children somewhat quickly you can support a lot of vhosts without using much memory since each one doesn't need to have a running process. Only hosts actually being accessed will have running processes. -Rasmus