Is a Slice 256 enough for Apache2 + Passenger hosting AT LEAST 4 Rails sites?

Is a Slice 256 enough for Apache2 + Passenger hosting AT LEAST 4 Rails sites?

I've a Slice 256 with 4 Rails 1.2.6 sites running pretty decently on Lighttpd + FastCGI (Ubuntu Server 8.04 LTS upgraded from 6.06 LTS); although it's such and old configuration, it's proven reliable enough for my smallish websites.

Now I'd like to upgrade some to Rails 2.x and I'm wondering if the same Slice 256 can take an Apache2 + Passenger configuration, since it worked great on my local development Linux box.

So my question is: Is a Slice 256 enough for Apache2 + Passenger hosting AT LEAST 4 Rails sites?

Any advice and experiencies on this will be greatly appreciated.

Generating a unique file path with Polymorphic Paperclip


How do you append a filter to the very end of a filter chain from a superclass?
In case anyone is confused, the asker is probably refering the 256 MB VPS at
Methodology for a Rails app
And to answer your question: It depends..
Extension/plugin/module system for a Ruby on Rails application?
Could you run four Twitters, of course not.

Newbie question attribute from associated table not showing up in index view
Could you run 4 sites that will have 1 (or less) concurrent user between them then yes, you could..
Quick and easy Slicehost slices

Capistrano + thin + nginx with user not allowed to sudo howto?

File storage in Heroku - alternatives? [closed]


I'd say no.

I'm assuming what you mean by "4 sites" is 4 rails instances.

2 is probably a better fit for a 256MB slice, and even that may be pushing it if you need to run cron/rake tasts or things like that..


I'm not entirely sure about moving from 1.2 to 2.3.

I do know that moving from 2.2 to 2.3 has some features to save memory (more specifically with routes).. If these are production sites, I would recommend setting up a new 256 slice and trying the upgrade.

It's good to have a development slice anyways..


In my experience; running a simple Typo blog would frequently consume more than 64M of memory on a shared host with basically no traffic.. A large, 100+ resource 2.3 Rails app with Memcached, all the bells and whistles, etc.

will sometimes hit 420MB of memory.. Of course, the answer really is "it depends".

It depends on your code, your traffic, your server, your database schema, your table indexes, etc..


Passenger advices that u use a pool of two passenger children on a 256-slice.

This means that it can process two parallel requests at the same time.

(correct me if i'm wrong about that one) So as Nick was saying, it all depends on how many hits your (clients) sites are getting..

70 out of 100 based on 50 user ratings 400 reviews