Right, this is along the same lines, but not generalized. They made
Lighty Memcache aware, but that doesn't do much for other applications,
e.g. our XSLT processor which can only access files. Further more, since
it's not generalized, the cached data cannot easily be shared by many
unrelated applications. So, if different applications employ their own
Memcache caching strategy, a lot of memory is waisted on duplicate data.
Though, embracing this idea, one could use Lighty + modmemcache + webdav
+ fuse but that sounds very slow :)
Best,
Erik Osterman
Rob Sharp wrote:
Hi all,
Curious if anyone has gone down the route of creating a fuse filesystem
implementation around Memcache, kind of along the lines of CacheFS.
It looks like others have had similar thoughts - lighttpd have a
mod_memcache module which caches small files in memory for faster access.
http://trac.lighttpd.net/trac/wiki/Docs%3AModMemCache
"Serving several thousands small files for lighttpd is quite
challenging. Operating System has to do a lot of random access, which
increase io-wait. mod_mem_cache is the plugin which stores content of
files in memory for faster serving. It's more configurable than OS
buffers (at least, linux buffers), in some cases yields better
performance.
For example, you can configure it to cache files smaller than 5 kb,
just cache files with a specific mime type or different strategies to
free memory when the configured limit has been reached."
Thanks,
Rob.
*Rob Sharp*
Lead Developer
Sound Alliance
inthemix : FasterLouder : Thought By Them : SameSame
100% recycled electrons were used for the composition of this email
- please don't print it unless you need to!
