Re: Issue 275 in memcached: binary protocol TOUCH,GAT,GATQ bug
Comment #10 on issue 275 by semnan...@gmail.com: binary protocol TOUCH,GAT,GATQ bug https://code.google.com/p/memcached/issues/detail?id=275 not fixed i use install make test and give me this page link. i send using php test poster to qa. please check it. debian wheezy dot deb memcached 5.5.17-1~dotdeb.1 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue 381 in memcached: Incomplete command does not result in ERROR response
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 381 by tgrab...@cloudius-systems.com: Incomplete command does not result in ERROR response https://code.google.com/p/memcached/issues/detail?id=381 What steps will reproduce the problem? 1. echo -n get key | nc -C localhost 11211 What is the expected output? What do you see instead? I'd expect the server to reply with CLIENT_ERROR or ERROR, depending on the parsing state. However the server currently does not send any reply. What version of the product are you using? On what operating system? 1.4.20 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue 275 in memcached: binary protocol TOUCH,GAT,GATQ bug
Comment #11 on issue 275 by dorma...@rydia.net: binary protocol TOUCH,GAT,GATQ bug https://code.google.com/p/memcached/issues/detail?id=275 that's not a version of memcached. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Max number of concurrent updates for a same key at same time in memcache.
Hi all, Reading memcache documents its clear that it can handle a very heavy load of traffic. However I was more interested in knowing the bound on how may updates for a specific key at the same time can memcache handle. -Shashank -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Max number of concurrent updates for a same key at same time in memcache.
Internally, there's a per-item lock, so an item can only be updated by one thread at a time. This is *just* during the internal update, not while a client is uploading or downloading data to the key. You can probably do several thousand updates per second to the same key without problem (like incr'ing in a loop). Possibly a lot more (100k+) What're you trying to do which requires updating one key so much? On Tue, 21 Oct 2014, Shashank Sharma wrote: Hi all, Reading memcache documents its clear that it can handle a very heavy load of traffic. However I was more interested in knowing the bound on how may updates for a specific key at the same time can memcache handle. -Shashank -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- --- You received this message because you are subscribed to the Google Groups memcached group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
