LiquidSDR's Liquid-DSP is a software-defined radio (SDR) digital signal processing library. This test profile runs a multi-threaded benchmark of this SDR/DSP library focused on embedded platform usage.
To run this test with the Phoronix Test Suite, the basic command is: phoronix-test-suite benchmark liquid-dsp.
* 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 25 July 2024.
Revision History
pts/liquid-dsp-1.6.0 [View Source] Mon, 19 Jun 2023 16:30:02 GMT Update against Liquid-DSP 1.6 upstream.
pts/liquid-dsp-1.0.0 [View Source] Tue, 09 Mar 2021 09:11:31 GMT Initial commit of LiquidSDR Liquid-DSP benchmark.
OpenBenchmarking.org metrics for this test profile configuration based on 486 public results since 20 June 2023 with the latest data as of 23 July 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 (Liquid-DSP 1.6 - Threads: 1 - Buffer Length: 256 - Filter Length: 32) 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.
Does It Scale Well With Increasing Cores?
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 Usage
Notable instruction set extensions supported by this test, based on an automatic analysis by the Phoronix Test Suite / OpenBenchmarking.org analytics engine.
Requires passing a supported compiler/build flag (verified with targets: sandybridge, skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Sandy Bridge (2011). Found on AMD processors since Bulldozer (2011).
Requires passing a supported compiler/build flag (verified with targets: skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Haswell (2013). Found on AMD processors since Excavator (2016).
Requires passing a supported compiler/build flag (verified with targets: skylake, tigerlake, cascadelake, sapphirerapids, alderlake, znver2, znver3). Found on Intel processors since Haswell (2013). Found on AMD processors since Bulldozer (2011).
Requires passing a supported compiler/build flag (verified with targets: cascadelake, sapphirerapids).
(ZMM REGISTER USE)
The test / benchmark does honor compiler flag changes.
Last automated analysis: 17 January 2022
This test profile binary relies on the shared libraries libm.so.6, libc.so.6, libliquid.so, libfftw3f.so.3.
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.
CPU Architecture
Kernel Identifier
Verified On
Intel / AMD x86 64-bit
x86_64
(Many Processors)
Loongson LoongArch 64-bit
loongarch64
Loongson-3A6000
ARMv8 64-bit
aarch64
ARMv8, ARMv8 Neoverse-N1 160-Core, ARMv8 Neoverse-V2 72-Core, Apple M2
