Re: ignored patches

From: Date: Tue, 04 Dec 2007 00:05:38 +0000
Subject: Re: ignored patches
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-33616@lists.php.net to get a copy of this message
Hi Stats, Everybody is providing clear and proven results. You are the only one who is throwing around hypothetical numbers (that 5% figure comes out of your head). Can you please be more responsible and provide some real results ? Also, pretty much every feature of a language can be abused. From my point of view, using autoload for every class IS abusive (as we all know, thanks to many benchmarks, that it affects performance negatively). But I don't defend its abolition because of that. Thank you kindly, Nicolas. On Dec 3, 2007 5:16 PM, Stanislav Malyshev <stas@zend.com> wrote: > > 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >

« previous php.internals (#33616) next »