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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
