CloudLinux on multiple cpu multi core system

[clm]

Wow 2500 vhosts, not bad

Our latest serever has slightly higher specs so maybe well be able to host more sites than planned.

@radoslav stefanov

You can estimate how many vhosts a server will be able to host. If you want to assing a CPU to a user than you can put 30 vhosts on a server with 32 threads and each one will be able to use 1 whole thread at any time. However this will never happen, you would be running at over 90% idle CPU at most times.

Even allowing 300 vhosts on 16 cores could be underselling depending on how much CPU you allow per user

On our previous configuration with suphp (uses alot more CPU than fastcgid) with 8 cores (not hyperthreaded) and 24GB ram we
e running hapily with a bit over 300 users.

[garybrooks]

4 disk raid 10 (600GB Disk 15K SaS) - Even better if you put MySQL on SSD
8 cores (16 with hyper-threading)
32GB of Memory
------------------------------------------------------------
no problem to host 2500 vhost and NOT oversell anything.

We run big Joomla sites on CloudLinux. Monitor your nodes thresholds, setup limits at all angles and just be sure to react if you hit a threshold.
Honestly, this is a math that you should NOT concern yourself with. Everyones hosting setup is a little different and not everyone understands how to tune a LAMP box to scale many vhost. If your smart, you will tune your box, work with LVE settings, and be happy that you found CloudLinux. CloudLinux is low enough cost, if you sold 100 accounts per box you could be profitable.

[radoslav]

Hello, Richard

Yes, I understand you can limit CPU, I/O and Memory on per account basis. The question here is not about overselling, I am against that. I am only trying to calculate, at least roughly how many websites this thing can handle.

If you could set (even reserve) every possible resource on account basis it would be a lot easier to measure and predict your revenue based on number of clients. (similar to VMs) Well at least for me. There are other ways to limit users that we are using, but custom configurations can give headaches with mainstream control panels, so we are looking for a better (less administrative) method.

Still, thanks for the reply. We will definitely give CL a try for some of our smaller servers.

[clm]

Hello,

CloudLinux lets you limit the amount of CPU, I/O and Memory each account can use and doesn actuellay reserve a CPU for an indiviual account. I do not see the point of reserving a single core to an account, On a server with 16 cores and 32 threads if you have enough ram and disk speed and capacity you should be able to host hundreds of accounts allowing quie a few accounts to use maybe two cores each.

If you are looking to supply quality hosting then you will obviously set higher limits and host less accounts then if you are looking to provide a cheap hosting plan.

Ive seen some hosts offering only 1/4 a core whereas we set the limit to at least one thread per site.

[radoslav]

Hello,

We are going to upgrade some of our hardware and considering getting CloudLinux for shared hosting environments. I must say your product looks promising, but need to ask a few questions.

My main concern is how doес CL deal with multi cpu/core systems. I would like to calculate (just rough) how many clients can a single box responsible for calculations handle (i/o and other stuff dont matter here, just cpu power). Of course there are fail over and load balance in between. But lets say you have a single 2x8 core with 3ghz per core server. Can you assign a single core/cpu to specific account/user/site for example out of the box ?
Thanks!