I think its basically saying that autoloading takes place after the script is compiled and while it's being executed (i.e. at runtime when PHP figures out a class is needed and not yet loaded, and so runs off to do so). Since the autoloaded files are not caught during compilation, it causes a headache for opcode caches.
That's a bit of a bummer... I think this means an opcode cache would still improve things - the file is cacheable, just not the actual class it contains. Pádraic Brady http://blog.quantum-star.com http://www.patternsforphp.com ----- Original Message ---- From: Stanislav Malyshev <[EMAIL PROTECTED]> To: Arnaud Limbourg <[EMAIL PROTECTED]> Cc: Zend Framework General <[email protected]> Sent: Thursday, November 30, 2006 9:32:10 PM Subject: Re: [fw-general] Opcode cache [was: Shared server load times] Arnaud Limbourg wrote: > You might want to read this, that shoould give enough info :) > > http://pooteeweet.org/blog/538/ Frankly, I don't understand from this message what is the problem. I understand APC has some problem caching something (what?) and for some (not explained) reason it's slow but I couldn't understand why. So far it looks like some internal APC issue, unless I am missing something. Does anybody have more detailed explanation of why autoload would be bad? -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited
