List of SiteGround Hosting Limitations

Last updated on

Here are the limitations for all SiteGround hosting plans:

StartUpGrowBigGoGeek
CPU Seconds 1000/hr
10000/day
300000/month
(7 minutes/hr)
2000/hr
20000/day
600000/month
(14 minutes/hr)
4000/hr
40000/day
800000/month
(18.5 minutes/hr)
Script Executions 1000/hr
10000/day
300000/month
(416/hr)
2000/hr
20000/day
600000/month
(833/hr)
4000/hr
40000/day
800000/month
(1111/hr)
Inodes 150000 300000 450000

In addition, no account is allowed to use more than 20% of the CPU for more than 10 seconds. Also, all cron job intervals are set to a minimum of 30 minutes.

SiteGround is very transparent about its resource usage limits and allows you to check whether you’re crossing the line at any given time. I personally think that it’s awesome, and a model for other hosts to follow. Here’s a page with the complete list of all SiteGround offers and discounts for hosting plans. I highly recommend them!

These limitations are applied on a “per account” basis. Meaning if you have multiple sites on a single account, the aggregate resource usage will be calculated. I personally love SiteGround (this site is hosted on it). Here’s a complete review of its features and customer service.

Checking your Resource Usage

SiteGround’s hosting limitations are very unambiguous. They allow you to easily check your resource usage so you know at all times whether you’re in danger of overstepping its limitations.

CPU Time Limits

When you log into your SiteGround cPanel, you see the graph on the left hand side showing you how many CPU seconds have been used in the past 2 hrs and 24 hrs.

CPU Seconds Limitations

The screenshot above will vary from plan to plan of course. Note that even though it shows the 2hr usage, SiteGround doesn’t explicitly have a limit for 2 hrs. Instead as you can see in the table above, the restriction is “per hour”, “per day”, and “per month”.

Script Execution Limits

Similar to CPU limits, you can check the number of script executions on the left hand side of cPanel as shown here:

Script Executions - SiteGround Hosting Limitations

The limit for a 24 hr period is usually 10 times higher than the limit for a single hour.

Inode Usage

The location for checking Inode usage on SiteGround is the same as for the other two.

Explanation of the Terms Used

If you’re new to these terms, they’re pretty confusing. Here’s a quick explanation of what they mean.

CPU Time Usage

The brain of the server is the CPU (Central Processing Unit). Today’s CPUs are so fast, that they can complete most tasks in milliseconds. The CPU time limit is the number of seconds a CPU actually works on your site for a given period of time.

Since there are only 3600 seconds in an hour, you might be wondering how the “GoGeek” plan allows 4000 seconds for a given hour! The answer is that CPUs have more than one “core”, and it’s possible (in theory) for all the cores to work for more than 3600 seconds on your site in any given hour.

However in reality, it’s extremely rare for a CPU on a shared hosting server to dedicate all its time to any single account. If it is, it’s an indication of a problem and a violation of the SiteGround hosting limitations. They will send you a warning and then throttle your site.

Script Executions

A “script” is a a program or process. Every PHP file ending with “.php” for example is a script. SiteGround’s script execution limits refer to the number of scripts your account processes for a given period of time. The quota goes up as your plan grows and you get more resources for your sites.

Inode Limits

And “inode” is a reference to a file or folder. Each plan has a specific number of inodes it allows. The more expensive plans allow you to have many more files and folders.

SiteGround Hosting Limitations Allow “Bursty” Websites

If you notice, the hourly limits are much higher than the daily limits. SiteGround recognizes for example that there may be periods when your site experiences unusually high traffic – like say a certain time of the day for example. During this time, your CPU usage and script executions will spike, and that’s OK!

What’s important is that your site calms down after a while and assumes a more sedate rate of resource consumption. So while the hourly limit for the GoGeek plan is 4000 CPU seconds/hour, you’re not allowed to do that for 24 hrs a day. Instead, the daily limit of 40,000 seconds puts a cap on how long your site can consume resources as a breakneck speed.

So instead of having a “hard” cap on resource usage per hour, it’s more of a “soft” cap. Your resource usage is allowed to spike temporarily to handle a sudden influx of visitors. But it’s up to you to ensure that you bring that down as soon as possible.

About Bhagwad Park

I've been writing about web hosting and WordPress tutorials since 2008. I also create tutorials on Linux server administration, and have a ton of experience with web hosting products. Contact me via e-mail!

Speak Your Mind

*