Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33580
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain synergy8.com designates 202.174.102.11 as permitted sender)
Reply-To: <scott.mcnaught@synergy8.com>
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>
Date: Mon, 3 Dec 2007 18:00:55 +1000
Message-ID: <003601c83582$a1b16fc0$e5144f40$@mcnaught@synergy8.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acg1fnqnJZGdxNibSwCYlrq1fQrO6wAAe5tw
Content-Language: en-au
Subject: RE: [PHP-DEV] ignored patches
From: scott.mcnaught@synergy8.com

I am a developer on a CMS also which uses the auto-include functionality to
include many classes over many files. Each request can include up to 30
different files.  The speed increase is around the 15% mark when combining
the files.  This is with APC installed too.

I heard rumours however that php6 is not going to have such an issue with
inclusion performance (something about caching of the inheritance tree in
APC?). 

I would just like to say that if there is still a performance issue in php6,
I would like to see the multiple namespaces per file functionality added.
But this is the only reason.
 

SCOTT MCNAUGHT
Software Developer

Synergy 8 / +617 3397 5212
scott.mcnaught@synergy8.com

-----Original Message-----
From: Gregory Beaver [mailto:greg@chiaraquartet.net] 
Sent: Monday, 3 December 2007 5:30 PM
To: Stanislav Malyshev
Cc: internals Mailing List
Subject: Re: [PHP-DEV] ignored patches

Stanislav Malyshev wrote:
> As for multiple namespaces per file, it adds certain complications, both
> syntax-wise and engine-wise, so I'm still not 100% convinced it is worth
> it.

Which are?

Remember, we both found, independently, that combining separate files
yields from a 10-30% performance increase.  I have only talked to 2
developers who would be using namespaces that don't want this feature.
Of course, these two developers are the only people who would be using
namespaces with commit access to the Zend/ tree, but that doesn't make
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.

Anecdotally, I heard of a recent file-combining optimization to a very
popular CMS that resulted in a 45% performance improvement.  Improving
the SQL queries led to only 9% improvement, so really the only reason
not to implement the multiple namespaces per-file patch is if you
actually *want* a large number of php devs to be annoyed at you :)

Thanks,
Greg

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php