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.
