Wireguard

AMD Ryzen 5 PRO 6650U testing with a LENOVO 21D3Z9VFUS (N3GET43G61.22 BIOS) and AMD Radeon 680M 512MB on Fedora Linux 36 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 2210044-NE-WIREGUARD37
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
View Logs
Performance Per
Dollar
Date
Run
  Test
  Duration
wireguard-1
October 04 2022
  17 Minutes


WireguardOpenBenchmarking.orgPhoronix Test SuiteAMD Ryzen 5 PRO 6650U @ 4.58GHz (6 Cores / 12 Threads)LENOVO 21D3Z9VFUS (N3GET43G61.22 BIOS)AMD Device 14b516GB256GB Kioxia KBG5AZNT256G LAAMD Radeon 680M 512MB (1899/400MHz)AMD Rembrandt Radeon HD AudioQualcomm QCNFA765Fedora Linux 365.19.11-200.fc36.x86_64 (x86_64)GNOME Shell 42.5X Server + Wayland4.6 Mesa 22.1.7 (LLVM 14.0.0 DRM 3.47)GCC 12.2.1 20220819btrfs1920x1200ProcessorMotherboardChipsetMemoryDiskGraphicsAudioNetworkOSKernelDesktopDisplay ServerOpenGLCompilerFile-SystemScreen ResolutionWireguard BenchmarksSystem Logs- Transparent Huge Pages: madvise- Scaling Governor: amd-pstate schedutil (Boost: Enabled) - Platform Profile: balanced - CPU Microcode: 0xa404102 - ACPI Profile: balanced - SELinux + itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + spec_store_bypass: Mitigation of SSB disabled via prctl + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Retpolines IBPB: conditional IBRS_FW STIBP: always-on RSB filling PBRSB-eIBRS: 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 Testwireguard-170140210280350SE +/- 4.69, N = 3331.20