Plans and Limits

How are PHP Executions Counted?

During each PHP Execution, a process on the server is spawned. That process is kept alive until the PHP logic inside the executed script is finalized and after that happens, a response to the web service is sent along with the termination of the spawned PHP process. Each PHP Executions is logged by the web server, and this allows for a precise calculation of the amount of PHP Executions to be retrieved from our Web Hosting Server. The amount is then presented to our customers so they can review it further and determinate whether or not their websites need to be optimized for a smaller hardware resource fingerprint.

How We Determine the Acceptable Usage Per Customer

We are constantly monitoring our customers' PHP execution frequency in our efforts to provide a stable hosting environment. Because our Shared Hosting services house more than a single user, we have to make sure each user utilizes only their allotted resources, and does not exceed them. Such excess could lead to server instability, potentially impacting other users.

Due to our efforts of keeping all resources in check, we have defined an acceptable count per Shared Hosting plan. Although the actual numbers will vary from month to month, 99% of our customers fall into the acceptable usage range. The range was specifically created with a buffer of over 10x the average usage to provide the best possible Shared Hosting experience. However, customers who fall outside the acceptable usage range are generally trying to host projects, which are well better suited for a VPS or Dedicated Server solution which do not have such quotas.

Based on the evaluation of more than 10 000 accounts per hosting plan, we have determined the following average PHP Executions per month:

*The lsphp Litespeed PHP binary execution available on the FastCloud Extra plan allows for spawning a process via which multiple executions are made for a certain amount of time. As all of the PHP executions made during that time frame will be counted as a single execution in your account's statistics, allowing for greater resource utilization.

What Happens When the PHP Executions Quota is Reached?

In order to ensure the best possible experience for our Shared Hosting users we a system in place that ensures users who exceed their monthly PHP Executions quota do not affect the rest of the server. The system will warn users about their increased PHP Executions usage, and ultimately - if they exceed their monthly quota - suspend their hosting account to prevent it from impacting the server's performance. As you can imagine that can lead to a loss of traffic and inconvenience for the visitors. However, we will never suspend a customer's hosting plan without proper warning beforehand. That is why the observation system we have in place will send users notifications once their resource quotas hit certain thresholds.

It can be best described as an early announcement procedure before the system actually takes action against user accounts that are reaching the limits.

• If 75% or more of the Script Executions have been reached the Observer service will open a Notice type report providing detailed information about the PHP Executions reaching 3/4 of their monthly quota;
• If 90% or more of the Script Executions have been reached the Observer service will open an Alert type report reminding the customer of the ongoing increase in PHP Executions and the potential consequences;
• If 100% of the Script Executions have been reached the Observer service will open an Incident type report informing the customer that the web hosting package has reached it's monthly quota. 72 hours after that report has been filed and if the customer has not taken action, the system will update it with information that the web hosting account has been temporarily put on hold, suspended, due to the lack of action.

Of course, the customer is provided with the option of temporarily re-activate their web hosting account. The temporary re-activation increases the Script Execution limit per month with 20% of the total amount of Script Executions based on the used Web Hosting package until the end of the current month. This action allows the customer to gain access to the web hosting account so measures can be taken for addressing the incident, but is not a permanent solution to any possible issues.