I just put the newest code into production. I'm going to monitor it for a
bit to see how it behaves. As long as there's no obvious issues I'll enable
reads in a few hours, which are an order of magnitude more traffic. I'll
let you know what I find.
On Monday, October 5, 2015 at 1:29:03 AM
It took a day of running torture tests which took 30-90 minutes to fail,
but along with a bunch of house chores I believe I've found the problem:
https://github.com/dormando/memcached/tree/slab_rebal_next - has a new
commit, specifically this:
In debian you can always grep the dpkg list
sysVoOdOo@stage02:~#dpkg -l | grep memcache
ii libmemcached10:amd64
1.0.8-1 amd64C and C++ client
library to the memcached server
ii memcached
1.4.13-0.2+deb7u1
Hi all,
I need to launch a handful of memcache instances at boot time as each one
is addressed to a different development environment, like this:
1. /usr/bin/memcached -m 16 -l 0.0.0.0 -p 1 -d -u nobody
2. /usr/bin/memcached -m 16 -l 0.0.0.0 -p 2 -d -u nobody
3.
Looking forward to the results. Thanks for getting on this so quickly.
I think there's still a bug in tracking requested memory, and I want to
move the stats counters to a rollup at the end of a page move.
Otherwise I think this branch is complete pending any further stability
issues or feedback.
