How many accounts per a server? On a basis of shared and reseller. Per a gig of ram, cpu ect...

This is always a tough question to answer as it has so many variables. You could technically host hundreds (if not thousands) of static websites on a powerful server yet only hundreds of moderately active dynamic sites, and perhaps only a few to a single site if it is extremely active and very dynamic.

We use a general figure for our servers at 200 accounts (not domains) per server. We may put less if we notice that for a particular server the loads are consistently high.

No server can have a specific # of accounts. I mean one server can have 300 accounts and another server that's the same have 600. It all depends on what kind of sites you have on there, the data and traffic.

We do the same. Server Core makes sure everyone gets what they pay for. Thats the most important thing. :)

On average we have about 198 per server.

Thanks guys, Seems like I'm getting 2 hundred.

The amount of accounts is not the way to go for, as it does not mean much.

What you should look for is

> Server load peak/low/average
> Disk I/O
> Server's ability to control the load
> Capacity of running log and stats updates, backups, daily crons like updatedb at the same time without crippling the server

Also it is a good idea to take in your average client usage growth into consideration, as you would not want to tell them that the server is too overloaded for them to add another site.

Hope I covered all the basics.

No server can have a specific # of accounts. I mean one server can have 300 accounts and another server that's the same have 600. It all depends on what kind of sites you have on there, the data and traffic.

Any host will have a minimum of accounts at a given price point, that needs to be placed per server, in order to run a profitable business.

The size of the accounts, or the CPU related policies (either public or internal), will simply reflect that need. (e.g. if you decide to offer forum hosting, you need to take into account that fact that you're dealing with heavy CPU usage, and size and price the packages accordingly.)

This is all the more important for smaller hosts, where the law of big numbers won't really apply, and where their first couple of filled servers really do have to be quite profitable.

Also it is a good idea to take in your average client usage growth into consideration, as you would not want to tell them that the server is too overloaded for them to add another site.

If the server is running too close to capacity, then either the plan was badly made (wrong assumptions on usage, which are quite likely when there's no real life data to use - new company), or some customers are effectively allowed to rob the company of its profits, because they're using more than they're paying. A careful host should approach these customers early on and work with them to find a solution before the server performance risks to be affected (i.e. adding one more site to it is immediately felt by everyone).

There is normally 100 to 150 (max) per server but whmcs just fills them up as we take orders/terminations e.t.c

100 to 150? WOW - thats very low.

We have 386 on the latest server and load remains well below 0.10 so I dont think there should be an issue for another few hundred accounts.

Also as cabron mentioned,

> Server load peak/low/average
> Disk I/O
> Server's ability to control the load
> Capacity of running log and stats updates, backups, daily crons like updatedb at the same time without crippling the server

These are important factors to decide how many accounts your server can manage.

It all depends on the type of website you host and the hardware you have.

Admins should be constantly monitoring the servers to give the most efficient use of them.