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,238 public results since 11 August 2016 with the latest data as of 19 February 2023.
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.
1 System - 4 Benchmark Results |
ARMv8 Neoverse-N1 - QEMU KVM Virtual Machine - Red Hat QEMU PCIe Ubuntu 22.04 - 5.15.0-1025-oracle - GCC 11.3.0 |
7 Systems - 318 Benchmark Results |
AMD Ryzen 9 5950X 16-Core - Gigabyte X570 AORUS PRO - AMD Starship Gentoo 2.9 - 6.1.9-gentoo-dist - KDE Plasma 5.26.5 |
6 Systems - 318 Benchmark Results |
Intel Core i5-12600K - ASUS PRIME Z690-P WIFI D4 - Intel Device 7aa7 Ubuntu 22.04 - 5.19.0-rc4-phx-three - GNOME Shell 42.1 |
5 Systems - 318 Benchmark Results |
AMD Ryzen 9 5950X 16-Core - Gigabyte X570 AORUS PRO - AMD Starship Gentoo 2.9 - 6.1.9-gentoo-dist - KDE Plasma 5.26.5 |
4 Systems - 318 Benchmark Results |
Intel Core i5-12600K - ASUS PRIME Z690-P WIFI D4 - Intel Device 7aa7 Ubuntu 22.04 - 5.19.0-rc4-phx-three - GNOME Shell 42.1 |
1 System - 5 Benchmark Results |
Intel Core i7-1065G7 - Oracle VirtualBox v1.2 - Intel 440FX 82441FX PMC Ubuntu 20.04 - 5.4.0-135-generic - 1.1.182 |
1 System - 5 Benchmark Results |
Intel Core i7-1065G7 - Oracle VirtualBox v1.2 - 1024MB Rocky Linux 9.1 - 5.14.0-70.13.1.el9_0.x86_64 - GCC 11.3.1 20220421 |