Re: MEMCACHED_SERVER_MEMORY_ALLOCATION_FAILURE (SERVER_ERROR out of memory storing object) error

2014-05-08 Thread dormando
> Dormando,Yes, have to admit - we cache too aggressively (just do not want to > use different less polite word :)). > > Going to do two test experiments: enable compression and auto reallocation. > Before doing this: > 1) why auto reallocation is not enabled by default, what issues/disadvantage

Re: Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

2014-05-08 Thread dormando
To that note, it *is* useful if you try that branch I posted, since so far as I can tell that should emulate the .17 behavior. On Thu, 8 May 2014, dormando wrote: > > I am just speculating, and by no means have any idea what I am really > > talking about here. :) > > With 2 threads, still solid,

Re: Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

2014-05-08 Thread dormando
> I am just speculating, and by no means have any idea what I am really talking > about here. :) > With 2 threads, still solid, no timeouts, no runaway 100% cpu. Its been days. > Increasing from 2 threads to 4 does not generate any more traffic or > requests to memcached. Thus I am speculating pe

Re: Issue 363 in memcached: MemcachePool::get(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Network timeout

2014-05-08 Thread notifications
I am just speculating, and by no means have any idea what I am really talking about here. :) With 2 threads, still solid, no timeouts, no runaway 100% cpu. Its been days. Increasing from 2 threads to 4 does not generate any more traffic or requests to memcached. Thus I am speculating perhaps it