Intel Core i5-8600K testing with a ASRock Z370M Pro4 (P4.20 BIOS) and eVGA NVIDIA GeForce GTX 1070 8GB on Pop 20.10 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 2104257-IB-WGTEST54239
Jump To Table - Results


Remove Outliers Before Calculating Averages

Graph Settings

Prefer Vertical Bar Graphs


Show Detailed System Result Table

Run Management

View Logs
Performance Per
April 26
  9 Minutes

wg_testOpenBenchmarking.orgPhoronix Test Suite 10.6.0Intel Core i5-8600K @ 4.30GHz (6 Cores)ASRock Z370M Pro4 (P4.20 BIOS)Intel 8th Gen Core32GB1000GB Samsung SSD 860 + 500GB Samsung SSD 850 + 1000GB Western Digital WD10EZEX-22M + 2000GB Western Digital WD2003FZEX-0 + 1000GB Western Digital WD10EZRX-00L + 1000GB Hitachi HDS72101eVGA NVIDIA GeForce GTX 1070 8GBNVIDIA GP104 HD Audio2 x 24G2W1G4Intel I219-VPop (x86_64)GNOME Shell 3.38.3X Server 1.20.9NVIDIA 460.674.6.0OpenCL 1.2 CUDA 11.2.1621.2.155GCC 10.2.0 + Clang 11.0.0-2 + CUDA 11.0ext43840x1080ProcessorMotherboardChipsetMemoryDiskGraphicsAudioMonitorNetworkOSKernelDesktopDisplay ServerDisplay DriverOpenGLOpenCLVulkanCompilerFile-SystemScreen ResolutionWg_test BenchmarksSystem Logs- Transparent Huge Pages: madvise- Scaling Governor: intel_pstate performance - CPU Microcode: 0xde - Thermald 2.3- itlb_multihit: KVM: Mitigation of VMX disabled + l1tf: Mitigation of PTE Inversion; VMX: conditional cache flushes SMT disabled + mds: Mitigation of Clear buffers; SMT disabled + meltdown: Mitigation of PTI + 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 generic retpoline IBPB: conditional IBRS_FW STIBP: disabled RSB filling + srbds: Mitigation of Microcode + tsx_async_abort: Mitigation of Clear buffers; SMT disabled

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 Testwg_test4080120160200SE +/- 0.44, N = 3177.74