The ability to reload cache from disk is major point to consider. There are many instances where a configuration change might have someone hard starting Cherokee several times - thus running with no cache for extended time should we not have a reloadable disk cache. Usually cold starts after crashes or extended outages are the most painful and thus Cherokee could become a good tool for many to avoid these troubled times :)
Unsure how the reads/writes to disk will overall perform. Seems like this Varnish does this - preallocates a single file at set amount of memory then reads and writes as it needs to. The startup time when spawning it fresh is unnoticeable on our gear and the pure throughput from Varnish immediately is very high. (Wish memcached would get on board with a similar to-disk feature). I'd be very interested in getting this new Cherokee cache accessible in some other abstract usable ways - like as a filesystem. It's still unclear how the cache will be tied-in and what access will be available. If it is like the current IO Cache in Cherokee - it will be transparent. Is this the idea? I would wish for more accessible feature - where we can fetch data on-demand from other apps - not just Cherokee per se. Finally, getting this new cache mechanism to transparently cache set item types from Reverse Proxy (like .gif, .jpg, etc. - static files - user defined) is the big powerful feature for us - should it be doable. Is that part of the cache strategy at this point? -Paul _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
