Our super-fast shared hosting comes with very few restrictions, but to keep things fair we’ve added a small selection – even though these will not apply to the majority of our clients who won’t go anywhere near the limits set.
A server’s resources, such as RAM (memory) and CPU (processor), amongst other things, are shared amongst all accounts on the servers supplied by us, for our cloud-based shared-hosting platform. We ensure that the server has plenty of capacity to meet the day-to-day needs of the vast majority of websites hosted, also ensuring that the demands for resources are met even at peak times.
Given that resources are shared amongst all users, this also makes it possible for web sites to use too many resources to the detriment of other customers hosted on the same server. This can happen for many reasons, but the most common causes are due to poor coding, compromised accounts or a very abnormal huge influx of visitors to the site.
Allowing sites to utilise more than their fair share of resources could lead to a poor quality of service for the remaining clients on the server. Therefore, we have drafted this policy to outline what we consider to be excessive usage of server resources, and to also exclude certain types of content and eliminate bad practices which almost always cause resource over-utilisation.
This policy stands in addition to our terms of service. The vast majority of sites won’t even come close to these limits, and those that do will almost certainly be adversely affecting the service other clients on the server are receiving.
We have developed a number of automated systems which enforce the bulk of our resource usage policy. These systems trigger alerts when accounts hit a ‘soft limit’ – these are mild violations of the resource usage policy that, whilst excessive, have not yet caused any significant reduction in server performance.
Typically we will then notify you of the problem, and you’ll have a period of time to fix the problem, usually between 3 and 7 days depending on the severity. This might be by rewriting parts of your site to be coded more efficiently.
If a site hits our ‘hard limit’, the server will automatically kill the process causing the problem to prevent the server being brought to a grinding halt, and may also suspend the website. This action will only be taken in extreme cases where the violation could have caused service failure or a severe degradation of service but where possible we will work with you to resolve any issues without interrupting your service.
These policies are in place to protect 99.9% of our customers from the tiny fraction of sites that cause performance issues. We want you to enjoy the best possible hosting experience for your site – that’s to say fast, and with the maximum possible up-time. The only way to do this fairly is to ensure that all users on our shared platform abide by the same set of principles, so no individual can become a ‘resource hog’ to the detriment of others.
Full details of our server load balancing can be found over at SimpleStack – our dedicated web hosting portal for clients.