>- see footer for list info -< Morning, I looking at a caching solution for my application and I am looking at publishing some of my pages as .cfm files so that when I use them I can access them via cfinclude. This has the added attraction of the fact I avoid cffile operations and they get stored in the template cache which will speed up access. The reason I can't just publish the whole page as HTML is because there are some dynamic elements in the page which I can't easily accommodate with JavaScript.
The approach I was thinking was to create the files when the page is first accessed, and then for the rest of the day use the cached version. Then at the end of the day purge the cache. Now I have in the region of 17,000 documents in my db that are available to access and each one could potentially produce 3 .cfm files for the cache. So before I put this together and benchmark memory usage and disk I/O are there gotchas you guys can think of? Also, this will potentially be more than the size of my template cache, this article (http://bit.ly/9T8rai) indicates that the cache can grow sensibly without causing issues and that it prioritises frequently accessed files. Is this described behaviour true in your experiences? Thanks. Simon Baynes www.simonbaynes.com Free online storage you can access anywhere:- http://www.simonbaynes.com/getsugarsync LinkedIn profile:- http://www.linkedin.com/in/simonbaynes _______________________________________________ For details on ALL mailing lists and for joining or leaving lists, go to http://list.cfdeveloper.co.uk/mailman/listinfo -- CFDeveloper Sponsors:- >- cfdeveloper Hosting provided by www.cfmxhosting.co.uk -< >- Lists hosted by www.Gradwell.com -< >- CFdeveloper is run by Russ Michaels, feel free to volunteer your help -<
