On 6 September 2012 19:22, dormando <[email protected]> wrote:
> It'd be a very specialized feature to do that, requiring outside > coordination to all daemons, blah blah. What people usually do is another > design pattern: > > http://code.google.com/p/memcached/wiki/NewProgrammingTricks#Avoiding_stampeding_herd > see "scaling expiration" in there. In short you set item expiration to be > as far as is reasonable, then use a "soft" expiration in the item. Then > you can apply things like scaling random refreshes. > > This works better since you can adapt it very specifically to your > application's particular needs. > Hi, Thanks for the reply the 'soft' expiration idea sounds like a good one. The benefit of having memcached 'stop expiring' would have been to easily get a similar effect without making any changes to the current application (other than telling memcachined to go into 'pause' mode) but I guess the soft expiry gets a similar affect for not too much work :) Thanks! Jon
