This test uses systemd-analyze to report the entire boot time.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark systemd-boot-total.
OpenBenchmarking.org metrics for this test profile configuration based on 1,241 public results since 11 August 2016 with the latest data as of 23 April 2024.
Below is an overview of the generalized performance for components where there is sufficient statistically significant data based upon user-uploaded results. It is important to keep in mind particularly in the Linux/open-source space there can be vastly different OS configurations, with this overview intended to offer just general guidance as to the performance expectations.
Based on OpenBenchmarking.org data, the selected test / test configuration (Systemd Total Boot Time - Test: Total) has an average run-time of 2 minutes. By default this test profile is set to run at least 1 times but may increase if the standard deviation exceeds pre-defined defaults or other calculations deem additional runs necessary for greater statistical accuracy of the result.
No, based on the automated analysis of the collected public benchmark data, this test / test settings does not generally scale well with increasing CPU core counts. Data based on publicly available results for this test / test settings, separated by vendor, result divided by the reference CPU clock speed, grouped by matching physical CPU core count, and normalized against the smallest core count tested from each vendor for each CPU having a sufficient number of test samples and statistically significant data.
Notable instruction set extensions supported by this test, based on an automatic analysis by the Phoronix Test Suite / OpenBenchmarking.org analytics engine.
This test profile binary relies on the shared libraries libm.so.6, libexpat.so.1, libz.so.1, libc.so.6.
This benchmark has been successfully tested on the below mentioned architectures. The CPU architectures listed is where successful OpenBenchmarking.org result uploads occurred, namely for helping to determine if a given test is compatible with various alternative CPU architectures.
3 Systems - 35 Benchmark Results |
QEMU Virtual 2.5+ - QEMU Standard PC - Intel 440FX 82441FX PMC Debian 12 - 6.1.0-18-amd64 - GNOME Shell 43.9 |
1 System - 5 Benchmark Results |
Intel Xeon Platinum 8370C - Microsoft Virtual Machine - 8GB Ubuntu 22.04 - 6.2.0-1016-azure - 1.3.238 |
1 System - 5 Benchmark Results |
Intel Xeon Platinum 8370C - Microsoft Virtual Machine - 8GB Ubuntu 20.04 - 5.15.0-1050-azure - 1.1.182 |
1 System - 5 Benchmark Results |
Intel Xeon Platinum 8370C - Microsoft Virtual Machine v7.0 - Intel 440BX Ubuntu 18.04 - 5.4.0-1109-azure - GCC 7.5.0 |
1 System - 1 Benchmark Result |
Unknown - O.E.M - Loongson LLC Hyper Transport Bridge openEuler 22.03 LTS - 5.10.0-60.116.0.143.oe2203.loongarch64 - GNOME Shell 3.38.4 |
1 System - 1 Benchmark Result |
Unknown - O.E.M - Loongson LLC Hyper Transport Bridge openEuler 22.03 LTS - 5.10.0-60.116.0.143.oe2203.loongarch64 - GNOME Shell 3.38.4 |
1 System - 3 Benchmark Results |
Unknown - O.E.M - Loongson LLC Hyper Transport Bridge openEuler 22.03 LTS - 5.10.0-60.116.0.143.oe2203.loongarch64 - GNOME Shell 3.38.4 |
1 System - 5 Benchmark Results |
Intel Core 2 Duo E8500 - LENOVO - Intel 4 DRAM + ICH10DO Garuda Soaring - 6.5.9-zen2-1-zen - KDE Plasma 5.27.9 |