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
So does every include besides main script (and prepend, but that's not so interesting) - you don't have any other way to include anything but execute include AFAIK. So either APC can't cache anything but the main script (which I believe is not the case - I don't know APC too much but from tests I know it is not a bad cache - and cache that can't do anything but main script would definitely be very bad) - or it can cache scripts loaded in runtime, which enables it to cache autoloads.
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 exactly my question - how? I'm not aware of any autoload-specific headaches for opcode caches. Maybe some of the headaches I know of are related to the autoload and I just don't see the link - but then I beg somebody to explain me the link.
I think this means an opcode cache would still improve things - the file is cacheable, just not the actual class it contains.
What do you mean here? If the file contains the class, then it IS the file, there's nothing to cache there besides that class (well, and main op array which is usually empty in this case). So I don't see how caching file and caching class can be different...
-- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/
