====== Account limits ======
Depending on the shared hosting plan level, your account is limited in several aspects at different levels.
You check on your resource utilization as described here:
* [[check-diskspace]]
* [[check-bandwidth]]
* [[check-processes]]
===== Virtualmin quotas =====
| ^Startup^Plus^Premier^
^Domains | 5 | 25 | 50 |
^Disk space | 5 GiB | 10 GiB | 20 GiB |
^Bandwidth | 15 GiB | 30 GiB | 60 GiB |
^Databases | 5 | 50 | 100 |
Limits on domains (virtual servers), databases, and disk space are //hard//, which means that Virtualmin will not let you create more virtual servers or databases and the file system will refuse to store more diskspace than what your limit is. The limit on bandwidth is //soft//, which means that your site will not be shut down and you will not be charged more if you go over the limit (we do monitor for significant abuses though).
===== Server resource caps =====
| ^Startup^Plus^Premier^
^Per account memory | 100 MiB | 175 MiB | 300 MiB |
^Per process memory | 75 MiB | 100 MiB | 150 MiB |
^Processes | 15 | 20 | 25 |
These caps are //hard//, which means that the operating system will not let you use more memory (per account memory limit applies to RSS, per process memory applies to total virtual memory, i.e. swap) or spawn more processes. The process limit is implemented on LWP level, and applies to lightweight processes or threads actually (may be triggered by a single thread-heavy process too).
Note that shell or SFTP sessions can do a good deal of pain to your resource utilization. Due to the way how SSH based sessions work (which applies to both full shell and SFTP connections) and how Solaris accounts for user/process accounting, each session takes up three process slots. Be careful not to leave sessions opened when not needed, especially if you like to open several sessions/connections at once, otherwise you might end up with all the process quota used up, and rendering the web server incapable of spawning any PHP processes for your website.