1 core, 2 cores, 2GB RAM, 4GB RAM, the question is only relevant if you have no expandability. Select your software, take its recommendation, and probably a little more, then make sure you can grow as needed.
Here is an example.
Let's say you go to AWS, get a server that is large enough to handle Magento. Your up, and in business. Now, business is good. Get another instance and split off your database. Business continues to grow, and you need a bigger Megento instance. No problem, snapshot your store, build a bigger instance, move your elastic IP, and retire your old one.
As long as you have the ability to grow, just worry about getting something that gets you in the game.
Kevin
Hi,
I am wondering what your opinion is on cores and RAM when using a VPS.
I am thinking about this in the context of Drupal and Magento, both of who are resource hogs.
I was told more RAM is much more valuable on a VPS than is the number of cores.
I'm assuming 4G of RAM is enough to not go into swap. I'm thinking this should be fine for a production site with moderate traffic running either Drupal or Magento.
As you know more cores means more money when it comes to VPS servers, while RAM is cheap.
Of course we know opcode cache, varnish, and memcache(d) can work wonders in speeding up websites. For this discussion lets assume we are using none of them.
The question is, will a second core make all that much difference if enough RAM is present to not use swap? How would I know I need a second core - look at the load?
And is there other consideration or things I should be looking at?
Thank you very much for all your feedback!!
Keith
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss