item expiration

Dave Cheney dave at
Wed Jun 11 02:22:40 UTC 2008

[dave at crimson ~]$ memcached -help | grep "exhausted"
-M            return error on memory exhausted (rather than removing  

On 11/06/2008, at 12:17 PM, Stephen Johnston wrote:

> You could run two memcached servers. One that only gets your long  
> lived items. Then you could size that cache based on your known item  
> sizes. Set the items to not expire and not add items to it. Then run  
> the other as your "active" server that you active add and remove  
> items to.
> On Tue, Jun 10, 2008 at 10:04 PM, Grant Maxwell <grant.maxwell at 
> > wrote:
> Hi Folks
> My understanding is that items will expire in two fundamental ways;  
> if a TTL was specified on the set or if the cache needs room and  
> deletes old items.
> My quesions are:
>        Is this understanding fully correct ?
>        Is there a way to tell the cache that an item should be fully  
> persistent - i.e. don't throw it away for any reason ?
> The second question relates to us being able to use the cache as a  
> storage area that only disappears if the daemon stops etc. This  
> would be very useful in our environment where we can cache stuff at  
> start up, share it across multiple processes/networks, and have  
> enormous impact on efficiency. Obviously not specifying a TTL on the  
> set method means it wont expire, but what about the situation where  
> the memcached needs space and deletes the oldest items ?
> thanks
> Grant

More information about the memcached mailing list