So we turned on cake caching and set the CACHE_CHECK flag in core.php to true. I've also set this in the controller: var $cacheAction = '1 hour';
In the tmp/cache/views directory, we see a cached copy of the page in question in there. So the page is being written to the cache as advertised. However, there is very little perceptible difference in load time between the cached version, and the non-cached version of the page. There's a mess of PHP code in the cache file "tmp/cache/views/filename.html.php". This seems to be loading the controller, and also models and all that stuff. Running Apache Bench confirms this: Standard page without caching: 22 requests per second Page with caching turned on to 1 hour: 21.67 rps (cache file was created) (we deleted it first) Text version of the page in webroot: 572 requests per second <b>Does Cake caching even work? How can a file be considered to be cached if in the cached version of the file, it does the following:</b> loadController loadModels instantiates the controller just loaded I can see where it may not include a few files in the framework, but unless I'm smoking something, there is no difference between doing this and just having it load the non-cached version of the page. Someone please tell me I'm smoking something, or that I just overlooked something somewhere really simple. - Ericson Smith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
