Includes free SSL certificate, unlimited bandwidth & fully optimised for WordPress.
Fully PCI-DSS compliant hosting, backups every 6 hours & free DDoS protection.
Unlimited bandwidth, WHM & cPanel control panel & fully white label.
Great value domain names available.
Create a professional looking website in minutes. Over 190 templates.
Speed up the delivery of your site.
Beautifully Simple. Massively Configurable. Scales from 1 VPS cloud, all the way up to a load balanced cluster.
Fully managed, high-spec dedicated servers deployed on our gigabit network, backed by our superior 24/7 UK support.
Instantly talk to one of our support team, we're here to help.
For our clients only. Open a ticket you can track and reply to.
Monday–Friday 9am – 8pm we're ready to assist you.
We pride ourselves on offering a hosting support service like no other; polite, knowledgeable & fast.
This article shows you how to check your cPanel account's memory, cpu and process usage has remained within limits. To ensure fair usage of the server's resources by our users, we virtualise individual requests made by your account and monitor these requests to ensure they do not:
If your cpanel account (including it's websites) exceeds the limits set by the package you are on, then you may notice that pages may be slow to load, or may even result in an error message.
This article assumes you are already logged into your cPanel account.
Step 1 - Access the Resource Usage stats.
Click the Resource Usage icon in the Logs area of cPanel.
Step 2 - Usage Overview
If your account has exceeded any of the limits you will be notified as below.
Step 3 - Selecting the timeframe
Ths screen is quite complicated so we will provide a brief overview only. At the top of the screen you are able to select a different reporting period from the Timeframe drop down box. The default timeframe is the last 24hrs. If you wish to view a different reporting period, then select it from the drop-down and click the Show button.
Step 4 - Understanding the graphs
The graphs show your allowed CPU usage, Virtual Memory usage, Entry Processes and resulting Faults.
CPU Usage : You are allowed to use up to the equivalent of an entire CPU core (100%). The most important factor here is the AVERAGE usage - if you see the AVERAGE hitting the maximum limit much of the time, then you need to address it. CPU is very prone to peak, and will often be one of the first resources to max out - so seeing the max value (blue line) hit the limit is not a sign of a problem, and is entirely normal - of course you want to throw all the CPU power you can muster at any task your account is running!
Virtual Memory Usage : This is the amount of memory your account has reserved from the system for use in your applications. We allow up to 1Gb of VMEM. While this account's average usage has remained reasonably low (the green line) this account is continually spiking through the max limit. Once your account exceeds the virtual memory limit, the system will not allow further memory to be allocated by your processes. This will cause virtual memory faults (vMf) to be recorded.
Entry Processes : This is the number of new processes your account creates. In the most simple terms, when you create a new connection to Apache, this is counted as an entry process. If your processes are very slow to run due to complexity, then a busy site may run out of available entry processes.
Faults : This graph shows the number of Entry Process (EP) faults and Virtual Memory Faults (vMem) being recorded by the system.