I just started a new thread "How to get more predictable caching behavior - how to store sessions in memcached" to discuss my more general question on how to achieve more predictability/reliability (I might have hijacked this thread a little bit, sorry for this).
Cheers, Martin On Mar 12, 6:43 pm, Les Mikesell <lesmikes...@gmail.com> wrote: > On 3/12/2010 11:21 AM, martin.grotzke wrote: > > > > >>> Hi, > > >>> I'm trying to follow this thread on my mobile, i hope i didn't miss > >>> anything. But AFAICS it was not yet explained, when memcached might > >>> drop cached data as long as there's enough memory and expiration is > >>> not reached. Or is this not deterministic at all? Perhaps you can > >>> point me to resources providing more details on this? > > >> 'Enough' memory may not be what you expect unless you understand how > >> your data fits in the allocated slabs. And I'm not sure what happens if > >> the keys have hash collisions. > > What about setting the minimum slab size to 1 mb (-n 1048576) so that > > there's only one slab and one can calculate with this? > > After seeing more of this thread, I'm inclined to think that the problem > that started it is really a misconfiguration or network issue. While > you shouldn't expect memcache to be a reliable store, the miss > percentage should not double when you add another server. > > -- > Les Mikesell > lesmikes...@gmail.com
