But yeah, hopefully you fixed it there.
I suppose we finnally found it.
I guess you might add those points to the timout wiki.
The problem seemed to boil down to the following:
vm.swappiness=60 (default) is a very bad idea, when combined
with deadline as a io scheduler.
symtom:
- after
Hi Dormando,
Just for curiousity, what's the client that you're using?
pecl/memcache-2.2.5
and reading http://brian.moonspot.net/php-memcached-issues
sounds like sticking to 2.2.5 is a good idea...
It may be inputting some junk data and memcached isn't responding since
it thinks it's halfway
well, I just used this tool to force enough requests :)
ok, I extended it a bit, for generating min/max/avg times of the
processes,
and for executing an explicit memcache get.
If you like, You can adopt my patches for redistribution:
http://www.maiers.de/memcache/mc_conn_tester.pl
IIRC
Hi,
we expirience memcache slow responses. (rare, only 3..5x per 24h)
I tracked the mecache timeout errors down to the following:
36278 13:52:46.020698 192.168.43.129 - 192.168.43.133 MEMCACHE get
key
36299 13:52:46.061557 192.168.43.133 - 192.168.43.129 TCP memcache
47127 [ACK] Seq=1 Ack=75
