Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33608
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Message-ID: <47548031.20608@zend.com>
Date: Mon, 03 Dec 2007 14:16:17 -0800
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Gregory Beaver <greg@chiaraquartet.net>
CC: internals Mailing List <internals@lists.php.net>
References: <4731278C.8020301@chiaraquartet.net> <4731F977.4080502@zend.com> <4753B087.4020206@chiaraquartet.net>
In-Reply-To: <4753B087.4020206@chiaraquartet.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] ignored patches
From: stas@zend.com (Stanislav Malyshev)

> Remember, we both found, independently, that combining separate files
> yields from a 10-30% performance increase.  I have only talked to 2

On synthetic benchmarks. On real apps, which do databases, calculations, 
network, etc. that would be probably no more than 5%, probably even 
less. And I don't see any application shipping in this format.

This is a very problematic issue - adding a feature into a language that 
serves only very specific very narrow performance scenario but which 
will inevitably be widely abused in cases which have nothing to do with 
that scenario.

> the feature unnecessary.  If you'd like, I could put you in contact with
> developers who have been struggling with combining files for several
> years now.

Why were they "struggling" - only problem existing with it is 
namespaces, and they certainly couldn't try to use namespaces for years? 
If they had other problems, they will keep having them and multiple 
namespaces per file are not going to help them.

> Anecdotally, I heard of a recent file-combining optimization to a very
> popular CMS that resulted in a 45% performance improvement.  Improving

Did they use bytecode caching?
Anyway, I have hard time believing PHP include is so broken, but if it 
is - it should be fixed, not through creating syntax-level workarounds 
but directly.

 > really the only reason not to implement the multiple namespaces per-file

I think I described my reasons now multiple times.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com