Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm considering to rent a VPS with 384 MB memory. It would run on CentOS and would have cPanel with Apache 2 / MySQL and Phusion Passenger with nginx / sqlite.

What do you think, will it have enough memory? It would serve around 10 small traffic PHP/MySQL websites and 3-4 small traffic Ruby on Rails app.

Thanks for your suggestions.

share|improve this question

migrated from Aug 27 '09 at 21:50

This question came from our site for professional and enthusiast programmers.


That really depends on your applications. You might want to consider running a VMWare image with the same OS and amount of memory allocated, deploying your 10 or so small websites to that image, and running a stress test against the image that emulates the approximate traffic you expect.

share|improve this answer

Why not run some tests locally with those sites, and measure their memory usage? It's too hard to say otherwise, without knowing exactly what your sites are doing.

share|improve this answer

I am presently running multiple VMs at work. With 256Mb I can comfortably run Apache on CentOS with PHP. So, you should be able to handle it with 384Mb. Unfortunately, if I am not able to run java/Tomcat on it until I increase the memory.

Depends on the kind of VPS technology used. If the provider uses OpenVZ/VServer, you will be able to save several tens of MB of memory from running the Linux kernel. However, if it uses something like Xen, you will need to spend some memory on the Linux kernel.

If you do not need to use Apache, avoid using it. There are plenty of other light-weight web servers around. You have already mentioned nginx. You can also try lighttpd and I think that many RoR sites use it.

share|improve this answer

There's no way you're going to be able to get acceptable performance out of that configuration. The 4 Rails apps will take more memory than that on their own, before you start looking at Apache and (especially) MySQL.

share|improve this answer

I strongly suggest that you don't install cPanel. Just cPanel alone will probably eat more memory than everything else combined. Manually configuring a small VPS isn't really too hard or time-consuming, especially if you use Google Apps to host your email and use your registrar's name servers.

share|improve this answer

You could just rent the VPS for a month and see how well it works. Many providers will let you upgrade your VM to a more expensive plan. (I know Linode makes this easy, for example.)

I expect that 384 MB will be just barely sufficient. It might work, but you might also want a little more headroom for safety's sake.

share|improve this answer

I'd go out on a limb and say you'd be pushing the limits of that vps, but its doable. You'd have to make sure you limited your rails apps to about one instance each and ran Php as fcgi ... then it might just work.

But I'm with alberge ... just go to and rent a 360MB linode ($20/month) and start setting up stuff to see how it goes ... Install and configure the Rails apps first, because thats where most of your memory will go.

Watch the memory with htop. Report back :D

share|improve this answer

the more memory you'll give the less it'll swap i.e. less I/O on disk i.e. faster, centos + apache + mysql by itself, but once you have your apps up and running it might run out of memory very quickly... today memory is very inexpensive so i suggest to bump it up more

share|improve this answer
Many VPS provider will not allow you to swap anything. – Lothar Sep 6 '09 at 12:39
ok, so then you need more memory on your box in order not to run out of memory assuming your application is somewhat decent and you going have some people come and use it – alexus Sep 8 '09 at 0:17

384 MB is a decent starting point. You may get better results if you don't use cPanel, though -- it starts a number of processes which aren't necessary on a single-user VPS and which will use up a significant amount of memory.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.