I think how Varnish does caching is worth looking at. It does in memory caching as well as storing cache data in a single predefined file that gets used and reused as a giant single block.
Having a file like this has overhead, but allows you to have hot cache in case of restart of Cherokee, server, etc. Nothing worse than cold empty caches after a restart - especially on cache-dependent sites that struggle with load when caching removed. In-memory for most used files makes sense. Make it configurable on amount of RAM to allocate to this cache and do same for providing size of disk cache. > I think I'll go for a in-memory-cache for the most retrieved files. The less > frequent requests will pass thru, while the top X petitions will be served > from the cache memory. Of course, X is configurable. > > Thoughts? > > -- > Octality > http://www.octality.com/ > > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
