4. Shared Systems and Resource Usage
Customers hosting on our shared environment may not use any shared system provided by Planet Margate in a way that interferes with the normal operation of the shared system, or that consumes a disproportionate share of the system’s resources. For example, excessive server hits, excessive bandwidth usage, excessive disk usage, inefficient scripts or database queries may compromise other users of the shared hosting environment. Planet Margate is authorised to suspend a user’s account should it be found that excessive resource usage is negatively impacting on other customers of our shared hosting environment. In most cases, the examples below do not apply to Planet Margate Dedicated servers.
4.1 Users may not, through a cron job, CGI script, interactive command, or any other means, initiate the following on Planet Margate’s shared servers:
4.1.1 Run any process that requires more than 50MB of memory space.
4.1.2 Run any program that requires more than 30 CPU seconds.
4.1.3 Run more than 10 simultaneous processes.
4.1.4 Send out mail to more than 500 recipients (email addresses) within one hour. 500 recipients represent one of the following: 500 recipients for one email, 500 individual emails or a combination of the two.
4.1.5 Send or receive, through mail, any file larger than 20MB.
4.1.6 Accumulate more than 2000 mail messages in a single pop mailbox. If the message count is exceeded, new messages will bounce to the original sender.
4.2 Should we discover that a customer is performing bulk mail runs on our shared systems that exceeds the limit communicated in 4.1.4 above, regardless of whether it constitutes SPAM or not, Planet Margate will deactivate the user’s account.
4.3 Custom server-side CGI scripts are to be run only by users with the appropriate package types (in Planet Margate’s case the Web Hosting Basic package or higher). No user may run CGI scripts for the benefit of external sites or services. The use of system resource limits is intended to prevent runaway CGI scripts on an unattended server. Also, processes with large memory footprints or hungry CPU requirements will incur swapping and other slowdowns that cause problems for every site on the server.
4.4 Interactive Web applications, commonly known as "chat", are not allowed on Planet Margate’s shared systems. These applications are better placed on dedicated servers.
4.5 MySQL databases are provided to users of the Web Hosting Basic package and higher:
4.5.1 Each qualifying individual package is limited to the allocated quota as published in the product matrix.
4.5.2 Each individual database is allotted a maximum of 500 MB disk space.
4.5.3 Databases may not be used for circumventing package disk allowances by storing web sites within the database.
4.5.4 Databases may only be used in conjunction with Planet Margate hosted packages. Access to databases from outside our local network is provided strictly for site and database development.
4.5.5 Only 10 concurrent MySQL connections per database user are allowed.
4.5.6 Databases may not be used to store binary files (including but not limited to image and application files). The database needs to reference the image on the user’s site rather than actually storing the image i.e. these files should be stored within the user account and referred to in the database by using a link.
4.5.7 Planet Margate reserves the right to require changes to databases and database usage should they have an adverse impact on a database server and/or other user databases on that server. Planet Margate may move the database to a new server, or in extreme cases, Planet Margate reserves the right to disable any database determined to be harming performance of a database server.
4.6 The use of "cron jobs" (processes that are run automatically at certain times, in accordance with a "crontab" file set up by each user), are allowed on Planet Margate servers, subject to the following conditions and restrictions:
4.6.1 To be used only by customers of the Web Hosting Basic package and higher.
4.6.2 The job must not execute more often than every two hours.
4.6.3 If a cron job is likely to consume excessive CPU usage, it should be given a lower CPU priority.
4.7 Resource limits are enforced by automatic monitoring systems. This is not applicable to Fully Managed Dedicated servers, providing that it does not interfere with Planet Margate’s ability to manage the server on the customer’s behalf.
