Thanks for explanation, Kevin, this was first time I tried to use caching, so I was little confused. After your explanation, and little playing with APC, I understand now. For anybody else who can find it useful, as Kevin mentioned, caching in ZF is all about the output caching (caching of output from function, class methods, DB queries, ...). The type of caching APC does (opcode caching) works AUTOMATICALLY, so you don't have to care about it at all. All you need to do is to install APC and tune a handful of directives if you like (not neccessary). APC takes care of the rest. Great product, really. With APC caching enabled, the initial delay after every request (when all needed ZF classes are loaded from harddisk) practically disappeared!!
Kevin Schroeder-2 wrote: > > You're thinking of 2 different kinds of caching. When thinking of the > type > of caching that Zend_Cache does, think *output*. Output from a given > function, page, class or block of code. The APC opcode cache is > completely > separate. However, APC does have a variable cache, which is what > Zend_Cache > is using to store that output when using the APC backend. If you are > running APC, it will automatically cache the opcodes for any files you > use, > but that is completely separate from Zend Framework. > > Kevin Schroeder > Technical Consultant > Zend Technologies, Ltd. > > -- View this message in context: http://www.nabble.com/Caching-of-MVC-and-other-ZF-components-tp15576554s16154p15597948.html Sent from the Zend Framework mailing list archive at Nabble.com.
