How to find the evacuation age? (version: 1.4.4)

Memcache evictions are based on least recently accessed items. (items which were not used for longest time gets deleted if the memory is exhausted). Is there a way to determine on a given time, for how long data is retained? Another way of asking - Can I tell how old is the next item to be evicte

Re: Issue 186 in memcached: Thread stack size should be set explicitly to reduce virtual memory usage

Comment #1 on issue 186 by thomassa...@gmail.com: Thread stack size should be set explicitly to reduce virtual memory usage http://code.google.com/p/memcached/issues/detail?id=186 http://www.thomasabosaleuk.com/

Re: How to find the evacuation age? (version: 1.4.4)

> Memcache evictions are based on least recently accessed items. (items > which were not used for longest time gets deleted if the memory is > exhausted). > > Is there a way to determine on a given time, for how long data is > retained? > > Another way of asking - Can I tell how old is the next ite

Binary DELETE with CAS

Hi, In the binary protocol, a client can send a DELETE request with a non- zero CAS. The server should delete the item only if the CAS matches. The release notes to memcached 1.4.0 specifically mention that CAS delete is now possible. Memcached code clearly supports it. But -- I'll refer he

Update Binary Spec to include value-type of Incr/Decr value

In reading the binary spec document http://code.google.com/p/memcached/wiki/BinaryProtocolRevamped it isn't clear that the value to be incremented/decremented must be the char representation of a number (0x31 for 1 for example) rather than an integer representation (e.g. 0x00 00 00 01) even though

Re: SASL and Python...

I just added SASL support to pylibmc. The pull request is still fresh: https://github.com/lericson/pylibmc/pull/31 On Feb 16, 7:23 am, Sam wrote: > Do any of the Python clients support SASL? > > Thanks.