3-network-wireguard

3-network-wireguard

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2405159-NE-3NETWORKW06
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
3-network-wireguard
May 14
  4 Hours, 16 Minutes


3-network-wireguardOpenBenchmarking.orgPhoronix Test SuiteQEMU Virtual 2.5+ (4 Cores)QEMU Standard PC (Q35 + ICH9 2009) (0.0.0 BIOS)Intel 82G33/G31/P35/P31 + ICH96GB107GB QEMU HDDvirtio_gpudrmfbQEMU GenericQEMU MonitorIntel 82540EMDebian 116.7.9 (x86_64)GNOME Shell 3.38.6X Server 1.20.114.5 Mesa 20.3.5 (LLVM 11.0.1 128 bits)GCC 10.2.1 20210110ext41280x800QEMUProcessorMotherboardChipsetMemoryDiskGraphicsAudioMonitorNetworkOSKernelDesktopDisplay ServerOpenGLCompilerFile-SystemScreen ResolutionSystem Layer3-network-wireguard BenchmarksSystem Logs- Transparent Huge Pages: always- CPU Microcode: 0x1- gather_data_sampling: Not affected + itlb_multihit: KVM: Mitigation of VMX unsupported + l1tf: Mitigation of PTE Inversion + mds: Vulnerable: Clear buffers attempted no microcode; SMT Host state unknown + meltdown: Mitigation of PTI + mmio_stale_data: Unknown: No mitigations + retbleed: Not affected + spec_rstack_overflow: Not affected + spec_store_bypass: Vulnerable + spectre_v1: Mitigation of usercopy/swapgs barriers and __user pointer sanitization + spectre_v2: Mitigation of Retpolines STIBP: disabled 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 Test3-network-wireguard11002200330044005500SE +/- 25.11, N = 35119.21