Question

I’m currently storing generated HTML pages in a memcached in-memory cache. This works great, however I am wanting to increase the storage capacity of the cache beyond available memory. What I would really like is:

1. memcached semantics (i.e. not reliable, just a cache)
2. memcached api preferred (but not required)
3. large in-memory first level cache (MRU)
4. huge on-disk second level cache (main)
5. evicted from on-disk cache at maximum storage using LRU or LFU
6. proven implementation

In searching for a solution I’ve found the following solutions but they all miss my marks in some way. Does anyone know of either:

• other options that I haven’t considered
• a way to make memcachedb do evictions

Already considered are:

memcachedb

• best fit but doesn’t do evictions: explicitly “not a cache”
• can’t see any way to do evictions (either manual or automatic)

tugela cache

• abandoned, no support
• don’t want to recommend it to customers

nmdb

• doesn’t use memcache api
• new and unproven
• don’t want to recommend it to customers

Answer 1

Seems that later versions of memcachedb can be cleaned up manually if desired using the rget command and storing the expiry time in the data record. Of course, this means that I pound both the server and network with requests for the entire data block even though I only want the expiry time. Not the best solution but seemingly the only one currently available.