wireguard-t
AMD Ryzen 7 3800XT 8-Core testing with a ASRock X570S PG Riptide (P2.20 BIOS) and NVIDIA RTX A2000 6GB on Debian via the Phoronix Test Suite.
Realtek Killer E3000 2.5GbE
Processor: AMD Ryzen 7 3800XT 8-Core @ 3.90GHz (8 Cores / 16 Threads), Motherboard: ASRock X570S PG Riptide (P2.20 BIOS), Chipset: AMD Starship/Matisse, Memory: 64GB, Disk: 512GB ADATA SX8200PNP + 1000GB Samsung SSD 980 PRO 1TB + 500GB Western Digital WDS500G1B0A-, Graphics: NVIDIA RTX A2000 6GB, Audio: NVIDIA GA106 HD Audio, Monitor: Mi Monitor, Network: Realtek Killer E3000 2.5GbE + Intel 7265
OS: Debian, Kernel: 6.0.0-6-amd64 (x86_64), Desktop: KDE Plasma 5.26.4, Display Server: X Server 1.21.1.5, Display Driver: NVIDIA 525.60.13, OpenGL: 4.6.0, OpenCL: OpenCL 3.0 CUDA 12.0.89, Compiler: GCC 12.2.0 + CUDA 11.6, File-System: ext4, Screen Resolution: 3440x1440
Kernel Notes: Transparent Huge Pages: always
Processor Notes: Scaling Governor: acpi-cpufreq performance (Boost: Enabled) - CPU Microcode: 0x8701021
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Mitigation of untrained return thunk; SMT enabled with STIBP protection + 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 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.
Realtek Killer E3000 2.5GbE
Processor: AMD Ryzen 7 3800XT 8-Core @ 3.90GHz (8 Cores / 16 Threads), Motherboard: ASRock X570S PG Riptide (P2.20 BIOS), Chipset: AMD Starship/Matisse, Memory: 64GB, Disk: 512GB ADATA SX8200PNP + 1000GB Samsung SSD 980 PRO 1TB + 500GB Western Digital WDS500G1B0A-, Graphics: NVIDIA RTX A2000 6GB, Audio: NVIDIA GA106 HD Audio, Monitor: Mi Monitor, Network: Realtek Killer E3000 2.5GbE + Intel 7265
OS: Debian, Kernel: 6.0.0-6-amd64 (x86_64), Desktop: KDE Plasma 5.26.4, Display Server: X Server 1.21.1.5, Display Driver: NVIDIA 525.60.13, OpenGL: 4.6.0, OpenCL: OpenCL 3.0 CUDA 12.0.89, Compiler: GCC 12.2.0 + CUDA 11.6, File-System: ext4, Screen Resolution: 3440x1440
Kernel Notes: Transparent Huge Pages: always
Processor Notes: Scaling Governor: acpi-cpufreq performance (Boost: Enabled) - CPU Microcode: 0x8701021
Security Notes: itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Mitigation of untrained return thunk; SMT enabled with STIBP protection + 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 STIBP: always-on RSB filling PBRSB-eIBRS: Not affected + srbds: Not affected + tsx_async_abort: Not affected
Testing initiated at 3 January 2023 17:09 by user user.