WireGuard 3950X

AMD Ryzen 9 3950X 16-Core testing with a Gigabyte X570 AORUS MASTER (F11 BIOS) and Gigabyte AMD Radeon RX 5600 OEM/5600 XT / 5700/5700 8GB on Arch Linux 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 2004216-VE-WIREGUARD35
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
WireGuard 3950X Arch Linux
April 21 2020
  11 Minutes


WireGuard 3950XOpenBenchmarking.orgPhoronix Test SuiteAMD Ryzen 9 3950X 16-Core @ 3.50GHz (16 Cores / 32 Threads)Gigabyte X570 AORUS MASTER (F11 BIOS)AMD Starship/Matisse32GB1000GB Samsung SSD 970 EVO Plus 1TB + 2000GB Samsung SSD 970 EVO Plus 2TB + 4001GB My Passport 25E2Gigabyte AMD Radeon RX 5600 OEM/5600 XT / 5700/5700 8GB (2090/875MHz)AMD Navi 10 HDMI Audio2 x C27HG7xIntel I211 + Realtek RTL8125 2.5GbE + Intel Wi-Fi 6 AX200Arch Linux5.6.5-arch3-1 (x86_64)GNOME Shell 3.36.1X Server 1.20.7 + Waylandmodesetting 1.20.7GCC 9.3.0 + Clang 10.0.0f2fs2560x1440ProcessorMotherboardChipsetMemoryDiskGraphicsAudioMonitorNetworkOSKernelDesktopDisplay ServerDisplay DriverCompilerFile-SystemScreen ResolutionWireGuard 3950X BenchmarksSystem Logs- Scaling Governor: acpi-cpufreq schedutil - CPU Microcode: 0x8701013- itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + spec_store_bypass: Mitigation of SSB disabled via prctl and seccomp + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Full AMD retpoline IBPB: conditional STIBP: conditional RSB filling + 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 3950X Arch Linux50100150200250SE +/- 0.75, N = 3217.51