testi

ARMv8 Cortex-A72 testing on Ubuntu 21.04 via the Phoronix Test Suite.

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2107050-IB-TESTI617094
Jump To Table - Results

View

Do Not Show Noisy Results
Do Not Show Results With Incomplete Data
Do Not Show Results With Little Change/Spread
List Notable Results

Statistics

Show Overall Harmonic Mean(s)
Show Overall Geometric Mean
Show Wins / Losses Counts (Pie Chart)
Normalize Results
Remove Outliers Before Calculating Averages

Graph Settings

Force Line Graphs Where Applicable
Convert To Scalar Where Applicable
Prefer Vertical Bar Graphs

Table

Show Detailed System Result Table

Run Management

Highlight
Result
Hide
Result
Result
Identifier
View Logs
Performance Per
Dollar
Date
Run
  Test
  Duration
Testi-wg
June 18 2021
  1 Hour, 58 Minutes
wg0 test
July 05 2021
  1 Hour, 32 Minutes
Invert Hiding All Results Option
  1 Hour, 45 Minutes


testiProcessorMotherboardChipsetMemoryDiskGraphicsMonitorOSKernelDesktopDisplay ServerCompilerFile-SystemScreen ResolutionTesti-wgwg0 testARMv8 Cortex-A72 @ 2.20GHz (4 Cores)BCM2835 Raspberry Pi 4 Model B Rev 1.4Broadcom BCM27118GB128GB SC128vc4drmfbLG Ultra HDUbuntu 21.045.11.0-1010-raspi (aarch64)GNOME Shell 3.38.4X Server 1.20.11GCC 10.3.0ext43840x2160LG TV5.11.0-1014-raspi (aarch64)OpenBenchmarking.orgKernel Details- snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 - Transparent Huge Pages: madvise Processor Details- Scaling Governor: cpufreq-dt ondemandSecurity Details- itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of __user pointer sanitization + spectre_v2: Vulnerable + srbds: Not affected + tsx_async_abort: Not affected

WireGuard + Linux Networking Stack Stress Test

This is a benchmark of the WireGuard secure VPN tunnel and Linux networking stack stress test. The test runs on the local host but does require root permissions to run. The way it works is it creates three namespaces. ns0 has a loopback device. ns1 and ns2 each have wireguard devices. Those two wireguard devices send traffic through the loopback device of ns0. The end result of this is that tests wind up testing encryption and decryption at the same time -- a pretty CPU and scheduler-heavy workflow. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgSeconds, Fewer Is BetterWireGuard + Linux Networking Stack Stress TestTesti-wgwg0 test400800120016002000SE +/- 20.15, N = 4SE +/- 18.30, N = 31759.081829.81
OpenBenchmarking.orgSeconds, Fewer Is BetterWireGuard + Linux Networking Stack Stress TestTesti-wgwg0 test30060090012001500Min: 1720.12 / Avg: 1759.08 / Max: 1815.37Min: 1803.81 / Avg: 1829.81 / Max: 1865.13