CloudLinux Reseller Limits
Has anyone been brave enough to deploy reseller limits to their production servers?
If so, has it made any difference?
++++++++++++++
If You want to buy cheap web hosting then visit http://listtop.pw and select the cheapest hosting. it can be suitable for all your needs.
Top 200 best traffic exchange sites http://listtop.pw/surf
Listtop.pw
Listtop.pw
Listtop.pw
+++++++++++++++
Has anyone been brave enough to deploy reseller limits to their production servers?
If so, has it made any difference?
You means the limits that allow providers to allocate a "pool" of resources to their resellers to do whatever they want to divvy it up? Like how some VM reseller packages works?
No, the latest version (beta) of CloudLinux allows an admin to place a CPU limit on a reseller so that they may not use more than a permitted amount of CPU in total.
Before there was just the limit per account, but now there is a limit in total!
(further clarification: the sum total of CPU for all the resellers' accounts cannot exceed this limit)
__________________
Harv45 (10-29-2017)
If you give a control of LVE settings to reseller then you would need to allocate some percent of CPU to the reseller.
This, of course, would lead to customers with only 10 sites that have access to 100CPUs total assigning 10 CPU to each of the sites. If the sites are badly coded this would put the significant load on a server.
__________________
www.24x7servermanagement.com
Server Management, Server Security, Server Monitoring.
Network Monitoring Team !! Skype: techs24x7
It's more like this.
The reseller has 20 users, so with the usual limited they would be able to use 20 CPUs, but the reseller limit is applied to limit the resellers accounts in total to 4 CPUs (400% CPU). Once the resellers users have reached 400% in total the sites start to slow down.
If you actually give individual users too lower a CPU limit individually it uses more CPU due to the added context switching, which is why it's recommended to offer 100% CPU or more per user.
If you actually give individual users too lower a CPU limit individually it uses more CPU due to the added context switching, which is why it's recommended to offer 100% CPU or more per user.
I am sorry but I am confused... Are you saying by allocating less than 100% of CPU dramatically increases overheads of CloudLinux?
That's doesn't even make sense as I heard the hardest Virtualization tech will draw about 5% at "worst" from the bare hardware.
I am sorry but I am confused... Are you saying by allocating less than 100% of CPU dramatically increases overheads of CloudLinux?
That's doesn't even make sense as I heard the hardest Virtualization tech will draw about 5% at "worst" from the bare hardware.
https://en.wikipedia.org/wiki/Context_switch
This may or may not help.
No, the latest version (beta) of CloudLinux allows an admin to place a CPU limit on a reseller so that they may not use more than a permitted amount of CPU in total.
Before there was just the limit per account, but now there is a limit in total!
(further clarification: the sum total of CPU for all the resellers' accounts cannot exceed this limit)
why i can not see this feature on my cloulinux? do they charge extra fee fro this feature?
why i can not see this feature on my cloulinux? do they charge extra fee fro this feature?
Check these links:- https://docs.cloudlinux.com/index.ht...er_limits.html
https://docs.cloudlinux.com/index.ht...er_limits.html
__________________
www.24x7servermanagement.com
Server Management, Server Security, Server Monitoring.
Network Monitoring Team !! Skype: techs24x7
If you will set the limit that will be best. Because assigning the unlimited resources will increase the server load. It is best to set the limit. CloudLinux has the option in which you can set the resource limit. It is best for all sites on the server as well as for maintaining the uptime of server.
I am sorry but I am confused... Are you saying by allocating less than 100% of CPU dramatically increases overheads of CloudLinux?
That's doesn't even make sense as I heard the hardest Virtualization tech will draw about 5% at "worst" from the bare hardware.
If you set a really low CPU limit, the machine will spend more CPU time suspending and unsuspending processes than it will executing code.
Remeber CloudLinux isn't about giving small resources per users it's about ensuring users have enough power by stopping abusers taking too much power.
(As well as clearing showing who is using that power)
If you set a really low CPU limit, the machine will spend more CPU time suspending and unsuspending processes than it will executing code.
Remeber CloudLinux isn't about giving small resources per users it's about ensuring users have enough power by stopping abusers taking too much power.
(As well as clearing showing who is using that power)
Ahh that make a lot more sense to me.
If you will set the limit that will be best. Because assigning the unlimited resources will increase the server load. It is best to set the limit. CloudLinux has the option in which you can set the resource limit. It is best for all sites on the server as well as for maintaining the uptime of server.
It's worth noting that before CloudLinux all providers except a couple that had custom kernels / kernel extensions were giving total access to every CPU to every account.
It's not impossible to maintain a server in this fashion - but you'll end up with far less capacity overall if you don't manually keep an eye on CPU usage on a regular and ongoing basis.
One of the things CloudLinux has really helped with is reducing the amount of time providers have to spend auditing usage and working with customers.
Out of many thousands of accounts we only have a few here or there that cross limits and we generally reach out and try to work with them to resolve those issues. These are the same accounts that we would notice and reach out to even without CloudLinux - except they would possibly impact others / the server as a whole for a brief period before we caught it.
$0.10
It's worth noting that before CloudLinux all providers except a couple that had custom kernels / kernel extensions were giving total access to every CPU to every account.
It's not impossible to maintain a server in this fashion - but you'll end up with far less capacity overall if you don't manually keep an eye on CPU usage on a regular and ongoing basis.
One of the things CloudLinux has really helped with is reducing the amount of time providers have to spend auditing usage and working with customers.
Out of many thousands of accounts we only have a few here or there that cross limits and we generally reach out and try to work with them to resolve those issues. These are the same accounts that we would notice and reach out to even without CloudLinux - except they would possibly impact others / the server as a whole for a brief period before we caught it.
Especially given that the tools that WHM comes with. If you just monitor the machine/VM itself 24x7 and then keep the eyes on the averages every now and then you should be in good shape.
However I agrees eventually this will be impractical for anyone and the costs associated of deploying and maintaining Cloudlinux will be well worth it in those circumstances.
If you increase limit then their would be access load on your server and it can slow your processing speed. So its better to use limit but their are also many features available in the marketing to increase your limit safely.
