* 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 22 April 2024.
Revision History
pts/ffte-1.2.1 [View Source] Tue, 29 Sep 2020 10:43:28 GMT Only build speed3d test that is used rather than make all to avoid a code issue elsewhere in codebase with latest GCC Gfortran.
pts/ffte-1.2.0 [View Source] Sun, 27 Sep 2020 14:17:57 GMT Update against FFTE 7.0, switch to speed3d for more demanding test.
pts/ffte-1.1.0 [View Source] Sun, 04 Mar 2018 11:35:47 GMT Update against FFTE 6.0, add Windows support.
OpenBenchmarking.org metrics for this test profile configuration based on 10 public results since 24 April 2019 with the latest data as of 13 March 2020.
Additional benchmark metrics will come after OpenBenchmarking.org has collected a sufficient data-set.
Based on OpenBenchmarking.org data, the selected test / test configuration (FFTE 6.0 - Test: N=64, 1D Complex FFT Routine) has an average run-time of 2 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 libgfortran.so.5, libm.so.6, libgomp.so.1, libc.so.6, libquadmath.so.0.
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.