Updates:
Status: Invalid
Comment #1 on issue 256 by [email protected]: PLEASE do not remove
cachedump, better dumping feature needed
http://code.google.com/p/memcached/issues/detail?id=256
Why not just run two memcached instances? One for short expiration times,
one for longer.
Or as a grosser hack, pad items with longer expiration times so they occupy
a different slab. Since each slab has its own LRU, you'd trade a few bytes
of overhead (it's not much at the smaller sizes) for "fast" reclaim.
But pulling the full list of keys back so you can find and fast reclaim
some is definitely the wrong way to do that. I tried to start a thread on
the mailing list a while ago for ideas on stats cachedump but nobody really
responded to it. In most cases what people want out of it isn't the best
usage of resources, and yours seems to be along those lines as well.
*but*, having said that, I have given thought recently to improving the
efficiency given your example traffic pattern. Given a few months time
memcached will probably just handle your situation better out of the box,
and you can use one of the above workarounds for now without having to
change core code and rely on your own fork in production.
For other people reading this issue; this is the sort of thing for a thread
on the mailing list. This isn't a bug report. If it were more focused on "I
have this traffic pattern and it's not very efficient" that would be more
on target.
If you wish to discuss this further please hit up the mailing list or open
a bug report on the real issue.
thanks!
