Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35708
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error)
Message-ID: <47BE029F.9000701@lerdorf.com>
Date: Thu, 21 Feb 2008 15:00:47 -0800
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: ceo@l-i-e.com
CC: internals@lists.php.net
References: <001c01c87264$3c01b4e0$b4051ea0$@de>    <58510.98.193.37.55.1203374232.squirrel@www.l-i-e.com>    <200802181936.17739.larry@garfieldtech.com>    <47BA34AB.6010408@lerdorf.com> <41103.98.193.37.55.1203622341.squirrel@www.l-i-e.com>
In-Reply-To: <41103.98.193.37.55.1203622341.squirrel@www.l-i-e.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Richard Lynch wrote:
> On Mon, February 18, 2008 7:45 pm, Rasmus Lerdorf wrote:
>> The idea here is that we want to be able to cache opcodes, classes and
>> functions and optimize them out of the runtime context so the executor
>> can skip creating classes and functions on every single request.  A
>> lot
>> of the traffic on this list over the past couple of months seems to
>> ignore this basic premise.  Features such as autoload and runtime
>> object
>> manipulation incur a huge performance hit in the sense that they
>> change
>> something that was free before and not only add the cost of the
>> feature
>> itself, but it also means the object in question now can no longer be
>> cached and has to be created on every single request.
>>
>> This doesn't mean we can't consider such features, but people need to
>> also consider the performance implications.
> 
> Many users need opcode caches and performance is crucial...
> 
> Many MORE don't, really :-)

That's a bit like saying that most people don't need more money.  While
probably true, it certainly doesn't hurt to have much lower page
latencies.  Similarly, most people don't need to scale either, but that
doesn't mean we should suddenly start tearing down our perfect shared
nothing sandbox.  If we design for good performance and scaling, the
trickledown effect means that even horribly-written applications will be
usable while the people who care about performance can get outstanding
performance out of it.

-Rasmus