krw at nobugz.com
Wed Mar 28 17:55:53 UTC 2007
I think you should just count on the LRU aspects of memcached to
handle that automagically. I do.
On Mar 28, 2007, at 10:44 AM, Andrew Harbick wrote:
> Similarly... Can memcached be configured (or does it already) to
> update the expiration every time an object is touched? The idea
> being that "hot" keys end up staying in the cached (even if they're
> never modified and recached).
> Jehiah Czebotar wrote:
>> On 3/28/07, Randy Wigginton <krw at nobugz.com> wrote:
>>> My question was not clear.
>>> An object is being stored to memcache with an expiration time. The
>>> process that wrote the object is dead/unavailable. Is there any way
>>> to query memcache with a specific key to determine how much longer
>>> the object will be available, or if it has already expired?
>> sorry i didn't quite answer the right question then; There is no way
>> to query memcached to see the expiration time (if any) for a given
>> key. The closest you can get right now is just to attempt to get the
>> key, and if it isn't there you can assume that either a) it was never
>> there, or b) it expired.
>> I recall this being discussed on the list some time ago, and there
>> talk of adding a way to query the expiration time; but i don't recall
>> ever seeing a patch go out for that
More information about the memcached