For Web Hosting accounts, you can view the differences in package values here: https://archhosting.net/website-hosting
The resource limits for each Web Hosting account is mentioned here:
|Memory||512 MB||2 GB||4 GB|
|Disk||2 MB/s||4 MB/s||6 MB/s|
Note: If recently updated, inodes will show inaccurately while quotas rebuild
Note: cPanel displays CPU usage as a maximum of 100% regardless of the internal settings
Your CPU limit is how much processing power your web hosting account is allocated. 100% allows for one core of usage. 200% would allow for two cores of usage, and so on. Physical cores on web hosting servers are 2.5 GHz with a max turbo frequency of 3.0 GHz.
Your memory limit is how much virtual RAM your web hosting account is allocated. Please note that after upgrading your plan, you may wish to change your PHP's memory_limit (via the MultiPHP INI Editor in your cPanel) to make use of the added memory.
Your disk limit is how much IO your web hosting account can consume at one time. If you exceed this limit, additional operations are throttled (not killed) until usage returns to normal. Cached disk operations (e.g. hitting the same file multiple times in a short period of time) will not contribute towards your IO usage.
Your IOPS limit is how many disk operations you may perform per second.
Your entry process limit is how many processes can enter your account's virtualization. For example, each concurrent connection spawned by Litespeed will count as an entry process. Processes generated by your account itself will not contribute towards entry processes.
Total processes accounts for how many processes you have running on your account. Once this limit is reached, no new processes may be spawned until one dies.
Essentially, an inode can be treated as a single file. If you create one file named "kitten.jpg" that will use one inode. If your inode limit is 5,000, you can store 5,000 files. A soft inode limit can be exceeded for a period of time, while a hard inode limit can not be exceeded at all.