Vedova Sagl reserves the right to suspend or terminate accounts found in violation of these items with or without prior notice given and without liability.
Vedova Sagl reserves the right to determine what constitutes resource abuse and take the appropriate action.
1. What's this all about?
The 'shared server' hosting environment is the hosting solution for our web hosting plans. A server’s resources, such as RAM (memory) and CPU (processor), amongst other things, are shared amongst all accounts on the server. We ensure that the server has plenty of capacity to meet the day-to-day needs of the vast majority of web sites, ensuring also 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.
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.
2. How are these policies enforced?
We have developed a number of automated systems which enforce the bulk 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 – typically between 2 and 10 days depending on the severity. This might be by rewriting parts of your site to be coded more efficiently, or if that’s not possible we can talk about alternative hosting solutions where you can have dedicated resources. 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 griding halt, and may also suspend the web site in line with our terms of service. This action will only be taken in extreme cases where the violation could have caused service failure or a severe degradation of service – 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 is to say fast, and with the maximum possible uptime. The only way to do this fairly is to ensure that all users abide by the same set of principles, so no individuals can become a 'resource hog' to the detriment of others.
If any of our policies are violated, this voids your eligibility for our money back guarantee.
4. Resource Usage Restrictions for Shared Plans
4.1 Apache Connections
No more than 40 simultaneous Apache connections are permitted from any one source.
Accounts are restricted to 15 concurrent MySQL connections.
Databases cannot exceed 2GB in size.
Database queries cannot exceed 8,000 per hour.
Database changes (insert/update/delete) should not exceed 2,000 queries per hour.
Accounts should not exceed an average of 1 second of CPU time per query for MySQL queries performed in any given hour.
Databases may not be accessed by externally hosted sites, except for the purposes of administering the database.
Attachments larger than 25MB in size should not be sent by email.
IMAP/POP Email Boxes must be no larger than 4GB each. Old mail can archived or deleted to remain below this limit.
No more than 60 POP connections are permitted per hour.
No more than 500 SMTP connections are permitted per hour.
No more than 250 emails may be sent per hour.
Outbound emails should not be sent to more than 50 recipients at any one time.
If you need to send mail to more than 50 recipients, mailing list software should be used. Any such software should be capable of throttling email sending to a maximum of 1 email every 5 seconds. Mailing software without this functionality is not permitted.
Mailing lists can have a maximum of 2,000 recipients. Users requiring mailing lists larger than 2,000 subscribers will require a cloud hosting solution or a dedicated server, or may use our email marketing platform.
Any mailing list over 1,000 recipients can only be sent between 3AM and 7AM UTC weekdays, or any time at the weekend.
Any emails sent to a mailing list must contain an unsubscribe link to an automated email removal system. This system must not be behind password protection.
SpamExperts Spam Filtering is available for up to 20 domains free of charge. Extra domains are chargeable.
4.4 Files & Folders
Accounts may not exceed more than 150,000 inodes. Every file or folder in your hosting account uses up one inode. The following accounts have an higher inodes limit:
- Platinum 2: 250.000
- Platinum 3: 300.000
- Platinum 4: 400.000
A folder cannot contain more than 5,000 immediate child files or folders, excluding files within child folders.
Any processes attributed to or initiated by your user account, must not:
Consume more than 256MB RAM.
Consume more than 60 seconds of CPU time.
Create core dumps.
Execute a script or binary that forks in a way to create a fork bomb, or spawn subprocesses.
Run in the background.
Listen to a network port.
Open more than 30 files.
Open or access a file greater than 2GB in size.
Run more than 40 simultaneous processes.
4.6 CPU Usage – Websites
The total usage of all websites running within an account may not exceed these limits:
Perform more than 1,300 dynamic page executions (PHP/CGI) in one hour.
Perform more than 13,000 dynamic page executions (PHP/CGI) in one day.
Consume more than 1,000 seconds of CPU time in one hour (realtime).
Consume more than 10,000 seconds of CPU time in one day (realtime).
4.7 Cron Jobs
All cron jobs must be ‘niced’ to 15 or greater (add nice -n 15 to the start of the cron job command).
No individual cron job within an account may exceed these limits:
Execute more than once per 5 minute interval.
Consume more than 30 seconds of CPU time per execution (realtime).
The total usage of all cron jobs running within an account may not exceed these limits:
Perform more than 36 executions in one hour (864 per day).
Consume more than 500 seconds of CPU time in one hour (realtime).
Consume more than 5,000 seconds of CPU time in one day (realtime).
4.8 Memory Usage
An account may not:
Consume more than 128MB RAM per second of CPU time consumed
You are not permitted to log into any other server or network from our servers.
4.9 Check your resource usage
You can check the resource usage for your account in real time from cPanel, at the 1H Software section.
5. Resource Usage Restrictions for semi-dedicated accounts
Semi-dedicated accounts have twice as much the resources of our shared plans described above.
5.1 Check your resource usage
You can check the limit for your account in the left sidebar of the cPanel.
6. Resource Usage Restrictions for VPS
The VPS limits are the resources listed on our website (CPU, RAM, disk space etc…).
A VPS cannot use 25% or more of system CPU resources for longer then 90 seconds. There are various processes and activities which can cause this; these include but are not limited to: Perl Scripts, CGI, PHP, Python, HTTP, etc.