Web Hosting Talk







View Full Version : S.A.D. Server Account Density


javierkatana
08-27-2008, 07:17 AM
I´m not saying that hosting 300 shared accounts in a server represent bad business model today, there are still 2 to 4 years to cash in from it and totally agree it’s a good strategy for long term medium/big players due to its cost effectiveness, but for startups?.

The shared account it’s a trend pushed by the industry to promote bandwidth and HD space wars, were little ones can´t compete; these 2 things we know 90% of the clients will never fully use, while not telling them that with just 30 simultaneous users posting in their forum or cms (300 online), will flag CPU/MEM usage alerts.

This is when the host wins with the TOS, but the client starts doing the “______sucks” at Google, because the client feels ripped off even if there´s no legal right to feel that way. In other markets with mature mainstream clients, this would be called “Dubious marketing”.

Something I like to call, “Server Account Density” will become the next sale factor, when clients start asking how many accounts are hosted per server; host providers with low S.A.D. ratios will capitalize on fairness and openness (Starting with an understandable TOS). Then, VPS accounts will become the standard, due to their advantage for controlling and distributing server resources, unlike shared accounts were 1 user can quite easily hog the server.

Well known companies for their shared account services and higher S.A.D. ratios will have to invest lots of money in servers to lower the densities, while maintaining the shared account system, but still avoiding the VPS licensing cost issues.

A Grateful Dad
08-27-2008, 09:15 AM
I think that's a good way to look at things - but I know lot's of hosts that successfully host 500 small accounts on a single server - it all comes down to load factors.

We have 4 SuperMicro Dual Xeon Servers - all with 4GB of RAM at this point and RAID 1 arrays using hardware RAID - not on-board or software.

These servers will easily handle 500 of our entry level hosting accounts - so long as you have a good back up, understand server load and are able to optimize to adjust to different variables.

On the other hand - these servers will only handle 350 of our mid line accounts and 225 of our high end accounts.

But the economics work out the same basically...

500 @ 6.95/mth = 3475.00/mth
350 @ 9.95/mth = 3482.50/mth
225 @ 14.95/mth = 3363.75/mth

It's all in how you manage loads and ensure you can deliver the QoS you promote.

I can truthfully say that our servers have handled the loads very well - and our last "outage" so to speak was a network blip in our upstream that lasted 12 minutes in April of this year.

The biggest thing I can say regarding "Server Account Density" is to take the time and work with the hardware to understand what it is capable of - not just wishful thinking of 500 accounts at $29.95/mth promising the world unlimited "everything" only to fall flat on your face when you start to get clientelle.

Good post!

/bin/false

Cats-Computing
08-27-2008, 10:59 AM
Indeed, but in deciding how many accounts to place on a server don't forget your target market. If you're targeting small 'home' based users with a blog or a personal website, they're hardly going to bring down the server if you know what I mean.

But if you're after clients with high traffic, database intensive sites, you'll need to adequately plan how many accounts per server, depending on your specifications of course.

All comes back to planning your business :)

huckyboy
08-28-2008, 10:21 AM
in relation to server account density, how do you guys allocate your clients? for example you have 3 plans and 3 servers of similar specs, Plan A 50MB disk space 5GB bandwidth, Plan B 100MB disk space 10GB bandwidth and Plan C 150MB 15GB.

Do you put Plan A clients in server 1, then Plan B clients in server 2 and so on? or just wait till server 1 fills up, then use server 2 next and so on?

not all of the time we would know if a client's site is the next big thing in the internet, or if would just be another website that sits idle most of the time where only friends and family visits them.

what are the things that you do that works for you when maintaining your server's account density?

A Grateful Dad
08-28-2008, 12:34 PM
We have server specifically dedicated to our clients...

So Server A houses all Plan A clients and Server B houses all Plan B clients and so on...

Works for us - we have not had any issues with this deployment method.

/bin/false