All shared hosting plans utilize CloudLinux technologies for increased security & server stability. Resource limits are in place to keep any account from causing problems for the rest of the server. You can view the current usage of these resources from within your cPanel account on the left menu.
- CPU: 100% of 1 vCore
- Memory: 1GB
- Processes: 50
- I/O: 5MBPS
- inodes: 300,000
- Starting mySQL Connections: 12 – max to 20
The number of inodes on your account is equal to the number of files located on your account.
When a file is opened, the server operating system reads the inode file. The more inodes you have, the more resources your account will use during its life – this includes resources while loading your website, uploading files etc. In the event your account hits it inode limits, you may be unable to upload files, make website edits etc. (note: inode limits are not “disk space” limits)
Shared cPanel accounts have a 300,000 inode limit per cPanel account. This limit helps ensure proper performance across all accounts in a shared environment.
How to remove or lower inode usage
The easiest way to lower your inode usage is simply remove unnecessary files and folders from your account. In short, if your website isn’t using it, remove it from your account. If you need assistance identifying the cause of a high inode usage on your account, don’t hesitate to reach out to our support department.
Getting the inode counts via SSH
If SSH has been enabled on your hosting account, you can utilize the following commands to get an inode count on your hosting account.
Use the command below while in the /home/ directory of your account to get a total inode count.
find . | wc -l
Use the command below to get a count of each directory located in the directory you are currently located in.
find . -printf “%h\n” | cut -d/ -f-2 | sort | uniq -c | sort -rn
Shared & reseller hosting accounts are limited to 100 emails per hour, per domain. This limit is in place to protect our servers from SPAM, whether it’s another customer attempting to SPAM or mass-mail or a website that has a large amount of blog spam. If you’re planning to send a large amount of emails, we always recommend using a 3rd party SMTP service to ensure your emails are not throttled.