* 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 19 November 2024.
Revision History
pts/hint-1.0.3 [View Source] Sun, 27 Sep 2020 10:34:33 GMT Drop DOUBLE option that has been not working.
pts/hint-1.0.2 [View Source] Tue, 14 Aug 2018 11:16:28 GMT Remove the INT test option as with latest hardware doesn't seem to finish or take hours unlike FLOAT and DOUBLE tests.
OpenBenchmarking.org metrics for this test profile configuration based on 386 public results since 26 February 2014 with the latest data as of 25 February 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 (Hierarchical INTegration 1.0 - Test: DOUBLE) has an average run-time of 26 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.
Based on public OpenBenchmarking.org results, the selected test / test configuration has an average standard deviation of 0.8%.
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.