Server Density removes Memcached because it's "too slow"

http://blog.serverdensity.com/2012/05/11/removing-memcached-because-its-too-slow/

by nphase • 14 years ago

17 6 14 years ago

blog.serverdensity.com

justinsb• 14 years ago

While I do agree that a good database can replace memcache in certain circumstances, isn't a 24ms response time from memcache a pretty good indication that something is seriously wrong there?

I'd expect <1ms, if your network allows you to get that from Mongo

relix• 14 years ago

It seems to me that the 24ms was the whole process they were using, i.e. put data in memcached, take data out using a seperate process, and put data in mongodb; versus putting the data straight into mongodb.

1SaltwaterC2• 14 years ago

Nope. From those metrics, Memcache is using all that time by itself. New Relic breaks down the network map based on distinct services. The database layer has a separate entry.

sauravc• 14 years ago

The title is pretty stupid not to mention misleading. 24ms to talk to memcache means "they're doing it wrong".

Server Density removes Memcached because it's "too slow"

Related Stories