Wireguard

Case closed / no active cooling

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

Statistics

Remove Outliers Before Calculating Averages

Graph Settings

Prefer Vertical Bar Graphs

Table

Show Detailed System Result Table

Run Management

Result
Identifier
Performance Per
Dollar
Date
Run
  Test
  Duration
RPi3B
September 15 2020
  3 Hours, 3 Minutes


WireguardOpenBenchmarking.orgPhoronix Test SuiteARMv8 Cortex-A53 @ 1.20GHz (4 Cores)raspberrypi rpi (2020.04 BIOS)935MB64GB SB64Gvc4drmfbFedora 325.8.6-201.fc32.aarch64 (aarch64) 20200904GCC 10.2.1 20200723btrfs720x480ProcessorMotherboardMemoryDiskGraphicsOSKernelCompilerFile-SystemScreen ResolutionWireguard BenchmarksSystem Logs- Scaling Governor: cpufreq-dt ondemand- SELinux + itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + spec_store_bypass: Not affected + spectre_v1: Mitigation of __user pointer sanitization + spectre_v2: Not affected + 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 TestRPi3B8001600240032004000SE +/- 41.83, N = 33653.98