This page compares the results of sustained cpu endurance tests on the selected VPS plans.
Endurance tests measure the ability of a VPS to sustain intense and prolonged CPU utilization. Each test consists of a CPU intensive task run in a loop continuously for 24 hours. The test targets an overall 50% CPU usage on the VPS.
Select one or more VPS plans:
Provider | Plan | Cost | Number of CPU cores | Trial | |
---|---|---|---|---|---|
Aruba Cloud | PRO VMware 8GB 4 cores | 87.60€ ($96.36) | 4 | Feb 09 2024 | Endurance Run details |
Aruba Cloud | PRO O8A16 | 55.50€ ($61.05) | 8 | Jun 26 2024 | Endurance Run details |
Aruba Cloud | PRO O2A4 | 20.10€ ($22.11) | 2 | Sep 23 2023 | Endurance Run details |
Aruba Cloud | VPS O4A8 | 11.79€ ($12.97) | 4 | Nov 08 2023 | Endurance Run details |
Aruba Cloud | PRO O1A2 | 13.20€ ($14.52) | 1 | Jun 23 2023 | Endurance Run details |
Aruba Cloud | VPS O16A32 | 31.29€ ($34.42) | 16 | Aug 08 2023 | Endurance Run details |
Aruba Cloud | VPS O1I1 | 2.49€ ($2.74) | 1 | Dec 24 2023 | Endurance Run details |
Aruba Cloud | PRO O4A8 | 31.20€ ($34.32) | 4 | Mar 24 2024 | Endurance Run details |
Aruba Cloud | CS O1A2 | 9.49€ ($10.44) | 1 | Sep 26 2024 | Endurance Run details |
Aruba Cloud | CS O12A24 | 102.20€ ($112.42) | 12 | Aug 11 2024 | Endurance Run details |
Aruba Cloud | VPS O2A4 | 6.29€ ($6.92) | 2 | May 11 2024 | Endurance Run details |
Server Optima | 200GB NVMe | $12.00 | 4 | Oct 06 2024 | Endurance Run details |
This is the average number of iterations the VPS executed every hour over 24 hours.
A higher number means the VPS is faster.
The coefficient of variation represents the stability of the VPS performance over the course of the test. It's the standard deviation divided by the mean number of iterations per hour.
A lower number indicates better stability.
This is the average proportion of CPU that is "stolen" by the hypervisor. A lower performance can often be explained by cpu steal running over 1%.
A higher number means the VPS host may be overallocated.
This is the average proportion of CPU left idle during the test. It simply serves to verify that the target 50% cpu usage was reached.