Hello everyone

I was searching for an answer for several days...but in vain.
I hope people here might have the answer.

I have several linodes....
On one hand I wish to maximize the ROI for each server so I host multiple domains on each.
On the other hand, If I check and see that there is some overload, I up-size the configuration to the next level.

My question is:
What is the best practice? or better yet, what gives the best value for money?
1. Single 10USD/mo per domain = Linode 1GB
(cost per domain 10USD/mo)
OR
2. 20USD/mo per multiple domains = Linode 2GB or higher
(cost per domain ? 2 = 10USD/mo , 4 = 5USD/mo)
My thoughts are:

Not all websites have heavy traffic or simultaneous traffic rush-hours
Stronger server - serves faster per domain, handles more websites, so each visitor enjoys faster browsing
Single sever per domain - cheap (relatively), hassle free, no worries about overload, same speed all the time (no other traffic but the single website)

Opt 1 vs opt 2:
Opt1: single domain, Opt2: 2 domains...So
Same price
Opt 2 gives better performence per page request as well as per load
Opt 1 easier to work with - downtime is only per the hosted domain

The above lists are just ideas running through my head as per pros & cons...

Any thoughts would be highly appreciated.
J.

_________________
http://nwg.co.il/

“Compassion is the basis of morality.” 
― Arthur Schopenhauer

You'll be fine starting out with multiple domains on a single Linode (1GB or 2GB, depending on your needs and expected load), and later upgrade (resize) that Linode to a different plan. If there's a very high load coming, you may also expand with multiple servers, and add on Linode's NodeBalancer service (for this to work, you'll need all Linodes in the same datacenter, though). Or, if you have a lot of static information on those websites/domains, you might consider adding caching/edge services, such as CloudFlare.

A $10 Linode might run a 100 sites or it might be insufficient to run one. The determining factors are:

(1) how the site is constructed: is it a heavy content management system, or is it text and images?
(2) how much traffic does it get?

Start small, add sites, monitor server performance, upgrade when need.

Also keep in mind that the user experience isn't determined solely by the power of the server. The user's Internet connection speed plays a large role. A site that makes fewer tcp connections, calls fewer & smaller resources (js, css images, etc.) will generally load quicker and provide a "faster" user experience. "Expires" and other techniques can be used to optimize the browsing experience independent of server power.

_________________
sleddog