Memory/Item sizes in 1.4.2

Hi, I've just been playing with the item size changes in 1.4.2, and I've noticed a few issues that I wouldn't class as critical, but that we probably ought to address somehow: 1) You can set the item size to be larger than the configured memory allocation: ./memcached -m 16 -I 128m

Re: Memory/Item sizes in 1.4.2

Hey, 1) You can set the item size to be larger than the configured memory allocation: ./memcached -m 16 -I 128m We should at least warn that the two values are somewhat incongruous. Maybe add this to the recent warnings discussion for cmdline arguments? I tossed this into that long

Is danga memcache is thread safe in java prospective???

Hi all, Please answer my question. Is danga memcache is thread safe in java prospective??? Thanx in adv.. ~karna

Re: decr returning not_found on valid keys?

Hey Tommy, On Wed, 14 Oct 2009 12:49:23 +0200 Tommy van Leeuwen chipa...@gmail.com wrote: Hello, I've been trying to debug something for a while. I have an app written in c using libmemcached. First i increment a key, if it returns not found, i set the key to a value of one. Next up

Re: Memcached user warnings

This would help weed out the basic configuration blunders. Cloud these also show up in the stats display. At the end? Warnings: 100% Misses, keys may be wrong. Memory waste over 50%. Threads greater than CPUs. Connections at or near the limit. Process swapping, size set too large