Running memcached in self, or in a separate, droplet?

  • Posted October 12, 2013

I’m thinking about using memcached and before reading I didn’t think of running memcached on a separate droplet/server.

Given, for example, that I had a 2GB droplet and would like to give memcached 2GB (just for keeping simple this example), what would you think of getting another 2GB droplet? and of having only one droplet but x2 capacity (4GB)?

Informed advice is much appreciated. Thanks!


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.

Pablo <br>That is a very good advice, thanks :)

IMHO, the more relevant factor is probably the number of CPU cores. Generally speaking, MySQL will perform better w/a multi-core VPS b/c it eats up a lot of resources. <br> <br>I would go w/this set-up: <a href=“”>How To Install Wordpress, Nginx, PHP, and Varnish on Ubuntu 12.04</a>, with either : <br> <br>1.) Your entire site on the $20/mo. droplet (you can always scale up, easily, if needed); or <br> <br>2.) Everything but MySQL on a $5 droplet + MySQL w/memcached on a $10 droplet. <br> <br>If monthly budget is not a limitation, check out either of the loadbalancing articles, as well.

I’ll be hosting a dynamic website with more read than write operations, kind of news site. Users will be able to log in but I expect to have anonymous traffic mainly.

It depends on the amount of load you’re going to put the servers through. What are you hosting on your servers? Website(s)? App(s)? Mostly static content? Or, mostly dynamic?