Provider News:
LayerStack releases managed database service
The sustained CPU endurance test runs a cpu intensive task in a loop for 24 hours. As maxing out the cpu might be considered abusive, the tests aims to use no more than 50% of each cpu core on the VPS.
The purpose of this type of test is
- first to evaluate the speed to the VPS,
- second to evaluate the stability over time of the cpu available to the VPS
- and third to detect VPS where the CPU is throttled and the performance goes down over time after cpu utilization goes over a threshold the provider considers excessive for a particular plan.
The performance is measured at regular intervals in terms of tasks executed per hour, amount of idle cpu and amount of "cpu steal".
| Description | Value | |
|---|---|---|
| Target CPU usage | Overall CPU that the endurance test tries to use across all CPU cores on the VM. | 50% |
| Average iterations per hour | Average number of tasks executed per hour. It represents how much work the VPS was able to achieve per hour. Higher numbers are better. | 18193 |
| Coefficient of variation iterations per hour | This represents the dispersion of the number of tasks per hour. It's the standard variation divided by the mean number of tasks per hour. It's an indicator on stability of the performance of the VPS. A low standard deviation means the VPS speed stayed close to constant. A high standard deviation means performance varied significantly during the test. | 1.83% |
| Average CPU idle | Average percentage of CPU that was idle during the test. This number should be close to 50% unless the CPU is being throttled like in burstable VPS plans. | 49.8% |
| Min CPU idle | Minimum percentage of CPU idle during the test. | 49.4% |
| Average CPU steal | Average percentage of CPU steal during the test. Lower is better. | 0.13% |
| Max CPU steal | Maximum percentage of CPU steal during the test. | 0.61% |
Number of tasks completed per hour
| Date | Number of iterations per hour | CPU Idle % | CPU Steal % |
|---|---|---|---|
| February 29, 2024 00:00 UTC | 17907 | 56.96 | 0.5 |
| February 28, 2024 22:00 UTC | 18057 | 49.77 | 0.11 |
| February 28, 2024 20:00 UTC | 18008 | 49.75 | 0.12 |
| February 28, 2024 18:00 UTC | 17920 | 49.77 | 0.18 |
| February 28, 2024 16:00 UTC | 18013 | 49.78 | 0.11 |
| February 28, 2024 14:00 UTC | 18053 | 49.78 | 0.1 |
| February 28, 2024 12:00 UTC | 18155 | 49.79 | 0.11 |
| February 28, 2024 10:00 UTC | 18029 | 49.79 | 0.12 |
| February 28, 2024 08:00 UTC | 18310 | 49.8 | 0.1 |
| February 28, 2024 06:00 UTC | 18565 | 49.79 | 0.08 |
| February 28, 2024 04:00 UTC | 18447 | 49.81 | 0.14 |
| February 28, 2024 02:00 UTC | 18456 | 49.8 | 0.21 |
| February 28, 2024 00:00 UTC | 18443 | 49.72 | 0.18 |
