We have a few thousands updates per second per box with memcached (linux with eight core each) and the box hardly reports any activity.
The only problem we had was the terrible slow .net serialization and the md5 computed when we plug hibernate with memcached. In my experience, the bottlenecks at the clients arise far more often than in the server. On 2/25/10, mariyan nenchev <[email protected]> wrote: > Well this is not actually true. I tried to update memcache before with about > 10 messages per second every second and it began to throw some IO > exceptions. I am using theese classes: > import com.danga.MemCached.MemCachedClient; > import com.danga.MemCached.SockIOPool; > The other code that manages my cached objects is my. > -- Sent from my mobile device Quidquid latine dictum sit, altum sonatur. ;-)
