* Uploading of benchmark result data to OpenBenchmarking.org is always optional (opt-in) via the Phoronix Test Suite for users wishing to share their results publicly. ** Data based on those opting to upload their test results to OpenBenchmarking.org and users enabling the opt-in anonymous statistics reporting while running benchmarks from an Internet-connected platform. *** Test profile page view reporting began March 2021. Data updated weekly as of 21 April 2024.
Revision History
pts/pennant-1.1.0 [View Source] Tue, 02 Feb 2021 10:01:47 GMT Fix unbounded OpenMP handling.
OpenBenchmarking.org metrics for this test profile configuration based on 187 public results since 30 August 2019 with the latest data as of 1 February 2021.
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 (Pennant 1.0.1 - Test: sedovbig) has an average run-time of 1 hour, 37 minutes. By default this test profile is set to run at least 3 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.
Notable Instruction Set Usage
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 libmpi.so.40, libm.so.6, libgomp.so.1, libc.so.6, libopen-pal.so.40, libopen-rte.so.40, libhwloc.so.15, libz.so.1, libudev.so.1.
Tested CPU Architectures
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.