CloudLinux Resource Limits: Difference between revisions

From Acenet Knowledgebase
Jump to navigation Jump to search
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 3: Line 3:
Acenet runs CloudLinux on our Shared hosting servers, to help us provide a balanced hosting environment.    To stop other users from starving your website of precious system resources, Cloudlinux proactively monitors resource usage, and limits account when they exceed a predefined usage limit.
Acenet runs CloudLinux on our Shared hosting servers, to help us provide a balanced hosting environment.    To stop other users from starving your website of precious system resources, Cloudlinux proactively monitors resource usage, and limits account when they exceed a predefined usage limit.


The predefined limits are 100% of 1 CPU Core, 1024MB physical memory, 4096kb Input/Output, and 20 simultaneous entry processes.
The predefined limits are 100% of 1 CPU Core, 1024MB physical memory, 4096 kb/s Input/Output, and 20 simultaneous entry processes.


==What CloudLinux regulates==
==What CloudLinux regulates==
Line 14: Line 14:


====Simultaneous Processes====
====Simultaneous Processes====
HTTP, SSH, CGI an dPHP connections all count toward this predefined limit, which is generous.  If your web site exceeds this limit, visitors receive “503 Error” messages in their web browser. The limit is primarily to help prevent DDoS, spambot, and brute force attacks from affecting the entire server. However, a poorly configured site can also cause this limit to be reached.
HTTP, SSH, CGI and PHP connections all count toward this predefined limit, which is generous.  If your web site exceeds this limit, visitors receive “503 Error” messages in their web browser. The limit is primarily to help prevent DDoS, spambot, and brute force attacks from affecting the entire server. However, a poorly configured site can also cause this limit to be reached.


====Input/Output (disk) usage====
====Input/Output (disk) usage====


If your account exceeds your I/O limit, CloudLinux will slow down your site while it is above the limit.  Your site remains online while being limited.  
I/O Limit is the maximum cumulative disk reads and writes. If your account exceeds your I/O limit, CloudLinux will slow down your site while it is above the limit.  Your site remains online while being limited.  


====MySQL Usage====
====MySQL Usage====

Latest revision as of 16:22, 14 September 2015

What is CloudLinux

Acenet runs CloudLinux on our Shared hosting servers, to help us provide a balanced hosting environment. To stop other users from starving your website of precious system resources, Cloudlinux proactively monitors resource usage, and limits account when they exceed a predefined usage limit.

The predefined limits are 100% of 1 CPU Core, 1024MB physical memory, 4096 kb/s Input/Output, and 20 simultaneous entry processes.

What CloudLinux regulates

CPU Usage

If you account tries to exceed 1 CPU core, CloudLinux slows it down. Your site remains online while being limited. When the usage drops below the max limit, CloudLinux stops slowing your site.

Memory Usage

If your account exceeds memory limits, visitors to your site will receive a "503 Temporarily Unavailable" error message in their web browser..

Simultaneous Processes

HTTP, SSH, CGI and PHP connections all count toward this predefined limit, which is generous. If your web site exceeds this limit, visitors receive “503 Error” messages in their web browser. The limit is primarily to help prevent DDoS, spambot, and brute force attacks from affecting the entire server. However, a poorly configured site can also cause this limit to be reached.

Input/Output (disk) usage

I/O Limit is the maximum cumulative disk reads and writes. If your account exceeds your I/O limit, CloudLinux will slow down your site while it is above the limit. Your site remains online while being limited.

MySQL Usage

The CloudLinux MySQL Governor monitors your account's MySQL Usage and restricts it based on CPU Usage, Disk Read/Write, and number of MySQL Connections.

No error messages are displayed when this restriction occurs. When usage falls below limits, MySQL Governor removes the restrictions. DDoS (Distributed Denial of Service), spambot, and brute force attacks, as well as plugins and unoptimized databases, are all possible causes of high MySQL usage.


Is your website hitting the limits?

You can check your resource usages inside cPanel, going to Logs -> Resource usage. If you hit any limits in the last 24 hours, there will be a summary on this page. You can also view charts and graphs by clicking on the details link.


Help, I am hitting a limit! How can I reduce my resource usage?

[1] You can try disabling plugins, disabling any special features, and/or repairing your database(s).

[2] You can look into optimizing your script(s). Your webmaster or the script developers should be able to assist with this.

[3] If you have addon domains, you may want to upgrade to a Reseller Hosting plan. A reseller plan will let you create separate cPanel accounts for your various addon domains. Since the Cloudlinux limits are on a per-cPanel account basis, that will let each of your domains have separate resources. For more information about our Reseller Hosting packages, please see our Reseller Hosting page.

Still need more resources?

If you're unable to reduce your account's resource usages, it is simply no longer suitable for a shared hosting environment. You might want to consider upgrading to one of our virtual servers if this is the case. You can view our virtual server offerings at our VPS Hosting page.

Our most basic virtual server offers an amazing amount of resources at a very fair cost. You can create additional Reseller or cPanel accounts with your own virtual server. If you go with a VPS with cPanel and our Managed Services Bundle, we will migrate your account(s) over to your virtual server for FREE.