Stanislav Malyshev wrote: > >> Yes and no. Rasmus Lerdorf has explained >> (http://pooteeweet.org/blog/538) >> that opcode caching is a compile-time optimization. Runtime inclusion of >> code happens after compile-time is past, and therefore cannot use the >> opcode >> cache. > > This is not correct. Each file is compiled by the engine separately, so > include can and are benefiting from opcode caching. >
Thanks for the correction, Stas. Is the explanation attributed to Rasmus in that blog out of date, talking about an older version of PHP & APC? Or is he talking about something else entirely? Rasmus' statements appeared to be pretty clear on the matter. Though I note that blog posting is now over a year old. Stanislav Malyshev wrote: > > BTW, we plan to solve these problems in 5.3 - so that all opcode caches > (that would bother to use the new stuff of course ;) will be able to > cache all files in 5.3+, regardless of how and when and in which way > they were included. > Great to hear! If only Achilles had been able to upgrade his heel in a similar way. :-) Will that be for Zend Platform's opcode cache only, or will it also help APC and Xcache? Regards, Bill Karwin -- View this message in context: http://www.nabble.com/Caching-of-MVC-and-other-ZF-components-tp15576554s16154p15600867.html Sent from the Zend Framework mailing list archive at Nabble.com.
