With our OpenVZ vServers (not to be confused with the KVM servers) you rent virtual cores that you share with other customers. Of course, they get a lot of work when you install, start and use some programs on your vServer. We check the load average to see if your server is overloaded. You can see the load of your server with the command „uptime„. We take the average of the last three numbers to calculate your load.
root@01234-56789:/# uptime 17:26:25 up 5 days, 21:13, 1 user, load average: 25.20, 24.23, 22.45
We have internally established the rule that describes the maximum allowed load of: 1.25 * number of cores booked
Cores | Max. Load |
1 Core | 1,25 |
2 Cores | 2,5 |
4 Cores | 6 |
6 Cores | 7,5 |
8 Cores | 10 |
We have integrated an automatism that cyclically monitors the average load of all virtual servers. We will lock your server if this automatism detects an overload 10x in a week. This ensures that no one overloads the host system and all customers can experience optimal service.
If your server is blocked, we will ask you for a statement. You will then have the following options:
- Upgrade the server package for a fee to get a higher limit
- Permanently reduce the server load
If you are not sure what is causing such a high load on your server, our support will be happy to help you.
Please note that during peak times (Friday evenings, weekends, holidays) everyone uses their vServer. Excessive load on one virtual server sometimes causes all other servers to react slower. Stay fair and try not to drive up the load on your server unnecessarily.
If you do not agree with this rule, we unfortunately have to terminate the prepaid relationship according to §7.2 (You are obliged to design your domain and the content accessible under it in such a way that an excessive load on our servers […] is avoided).