Hello,
I am shopping for a Linux VPS, on which I will run several
Drupal 4.7 based websites.
The only parameter I'm frankly unable to judge myself is the minimum amount of
RAM I should ask for, to make sure that that doesn't become the bottleneck. Assuming I have a pretty realistic idea of how much traffic I'd get in my the first year, how should I map that to RAM? Of course, even cpu speed is important, but that is something you can't change on a VPS plan, unlike RAM. Let's also ignore bandwidth, for simplicity.
Are there any (semi) official statistics or personal experience you can share as webmaster on this?
I'm looking for answers (or methods to find them) to questions like:
"how much RAM does one need to run Linux + Php + Mysql + Drupal 4.7 on a website with, say, 1000 nodes, without the RAM itself being the bottleneck?"
"does it change if I have one domain with 1000 nodes on one mysql database or 5 domains with 200 nodes each, all running from the same drupal install, but with
a separate mysql database for each"?
Please feel encouraged to elaborate or add any other side of the issue I might have forgotten.
Thank you in advance for any feedback,
O.
Comments
I don't think that the
I don't think that the number of nodes influences the RAM you need. The RAM is typically affected by the number of visitors you get and the number of modules you use.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
The RAM is typically
The RAM is typically affected by... the number of modules you use.
Is there any table or something which list how much RAM each module (OK, say the standard ones and the 20/30 more popular after them) needs?
TIA,
O.
No, but you can test this
No, but you can test this yourself. Simply install your site and decrease the php memory limit untill you get "not enough memory" errors. :p
For a typical Drupal site 16MB should be sufficient. If you only have very few modules, 8MB should suffice, if you run a lot of them, you will need 24MB.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
64MB if you're good.
The actual load of the system is the most important factor. How many hits/second? How many concurrent hits/users browsing? Do you need to survive the "slashdot effect"?
If you're doing sites with low usage, you should be able to run with 64MB. You'll want some experience of shoe-horning MySQL/PostgreSQL and Apache into a small space.
96MB makes it easy, and you should have no problems if you get 128MB.
You shouldn't NEED more than that for small sites.
-- Version Control your Drupal web site with The File High Club's Free Trial!
The actual load of the
The actual load of the system is the most important factor. How many hits/second?
I was hoping to find some formula/coefficient, even if only coming by popular wisdom, to map hits/second to RAM, something like "X MB is the bare minimum to make the system boot, then add Y MB each K hundred hit per second". Or at least to learn if and why the very concept of such a formula makes sense or not.
Thanks for your suggestions, of course. I'll re-check the VPS plans around 96/128 MB.
Any further input is still appreciated, of course.
O.