Running Memcache on separate droplet - Worth it?

  • Posted October 12, 2013

I’m considering running Memcache on a separate droplet, but need to do this in “Amsterdam 1” where private networking is not available. My concern is that communication between Apache and Memcache will be to slow over the droplets public IP addresses and that this will “eat up” most of the increased performance from using Memcache.

Anyone with experience or knowledge about this that have some qualified advice to give?


This comment has been deleted

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Running memcached on the public interface of a separate droplet in <strong>the same</strong> datacenter does not degrade its performance as it gets routed internally and not through the public internet (you can test it by running a traceroute from an AMS droplet to another AMS dropelt) so it will have the same performance of running on a private network. <br> <br>Just make sure you firewall your memcached droplet and you should be good to go :]

@kamaln7 Thanks for the answer. And what about replication of memcache based sessions between droplets not hosted in the same datacenter ? Its it safe and efficient ?

Thank you for the feedback, this was exactly what I was hoping for :-).