Hello,
On 12/3/06, Rasmus Lerdorf <rasmus@xxxxxxxxxxx> wrote:
Andi Gutmans wrote:
> Faster is always nice but the biggest and most noticable performance gain
> happens. I believe that the performance loss is significant in most
> real-world apps.
> I just pointed it out because PHP users who don't know internals who hear
> this kind of stuff think it's a real issue and start worrying about it, when
> they really don't have to.
How do you know? Have you profiled this extensively? I perfectly agree
that the majority of PHP users don't need the performance. They also
don't need an opcode cache. But we are already talking about the
smaller group of people interested enough in performance to use an
opcode cache,
Yes and I feel like most people worrying about this non issue will not
notice any performance impact. If the (relatively small) performance
improvement is important, they have changed their apps structure
already or have identified the bottlenecks (that must be an even
smaller group).
I agree with Andy that many (the majority) users are talking about
performance when they do not really know how their favorite
frameworks/set of packages work. They read that conditional includes
are evil and does not work with PHP/cache (it is not true per se, they
only misread a mail/post). But the problems are often in their apps
and nothing can be done against that but education, but that's not our
job.
By the way, the same applies to the include_once against include myth
(which is becoming as known as condition include).
But what can be done? Should "we" stop to talk about this only because
the possible confusions? :)
--Pierre
| 
