When to run more linodes for one site?
Will this make a significant change to disk I/O having separated between MySQL and PHP like this. Anyone have a rule of thumb for when to start considering this?
Thanks
6 Replies
Remember that throughput is not measured on a per-Linode basis. Add the throughput of all your Linodes within the same data center and divide it up as you like.
NOTE: I believe bandwidth is only pooled within individual datacenters. I'm not sure if it is pooled if you have one Linode in Atlanta and one in Newark.
BTW, I found a good internal resource (articles.linode.com) that talked a bit about when to start thinking about separating the db from the app and so on. Mentioning it just so that anyone else wondering can benefit from it.
You'd also not get any more reliability; if either server goes down, you're entirely down anyhow. Multiple DCs only make sense if you're going for redundancy; unless you can operate entirely off the resources in any given location, there's no point. Otherwise you'd still have the single-point-of-failure.
@carmp3fan:
NOTE: I believe bandwidth is only pooled within individual datacenters. I'm not sure if it is pooled if you have one Linode in Atlanta and one in Newark.
By coincidence I asked Array (Linode staff) this question on IRC early this morning and bandwidth is also pooled between datacenters.
Also by coincidence I have a Linode in Newark and another in Atlanta, and those were the very two that I was asking about.
In my case it was never the idea to use different data centers. It was to enable / create a scalable app that hopefully can better handle the volumes I see today.
So reliability and redundancy are of course still issues, but since I'm not a large corporation I think I have to try to live with that.