wg_test
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.
wg_test
Processor: Intel Core i5-8600K @ 4.30GHz (6 Cores), Motherboard: ASRock Z370M Pro4 (P4.20 BIOS), Chipset: Intel 8th Gen Core, Memory: 32GB, Disk: 1000GB Samsung SSD 860 + 500GB Samsung SSD 850 + 1000GB Western Digital WD10EZEX-22M + 2000GB Western Digital WD2003FZEX-0 + 1000GB Western Digital WD10EZRX-00L + 1000GB Hitachi HDS72101, Graphics: eVGA NVIDIA GeForce GTX 1070 8GB, Audio: NVIDIA GP104 HD Audio, Monitor: 2 x 24G2W1G4, Network: Intel I219-V
OS: Pop 20.10, Kernel: 5.11.0-7614-generic (x86_64), Desktop: GNOME Shell 3.38.3, Display Server: X Server 1.20.9, Display Driver: NVIDIA 460.67, OpenGL: 4.6.0, OpenCL: OpenCL 1.2 CUDA 11.2.162, Vulkan: 1.2.155, Compiler: GCC 10.2.0 + Clang 11.0.0-2 + CUDA 11.0, File-System: ext4, Screen Resolution: 3840x1080
Kernel Notes: Transparent Huge Pages: madvise
Processor Notes: Scaling Governor: intel_pstate performance - CPU Microcode: 0xde - Thermald 2.3
Security Notes: 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.
wg_test
Processor: Intel Core i5-8600K @ 4.30GHz (6 Cores), Motherboard: ASRock Z370M Pro4 (P4.20 BIOS), Chipset: Intel 8th Gen Core, Memory: 32GB, Disk: 1000GB Samsung SSD 860 + 500GB Samsung SSD 850 + 1000GB Western Digital WD10EZEX-22M + 2000GB Western Digital WD2003FZEX-0 + 1000GB Western Digital WD10EZRX-00L + 1000GB Hitachi HDS72101, Graphics: eVGA NVIDIA GeForce GTX 1070 8GB, Audio: NVIDIA GP104 HD Audio, Monitor: 2 x 24G2W1G4, Network: Intel I219-V
OS: Pop 20.10, Kernel: 5.11.0-7614-generic (x86_64), Desktop: GNOME Shell 3.38.3, Display Server: X Server 1.20.9, Display Driver: NVIDIA 460.67, OpenGL: 4.6.0, OpenCL: OpenCL 1.2 CUDA 11.2.162, Vulkan: 1.2.155, Compiler: GCC 10.2.0 + Clang 11.0.0-2 + CUDA 11.0, File-System: ext4, Screen Resolution: 3840x1080
Kernel Notes: Transparent Huge Pages: madvise
Processor Notes: Scaling Governor: intel_pstate performance - CPU Microcode: 0xde - Thermald 2.3
Security Notes: 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
Testing initiated at 26 April 2021 02:17 by user fi4o.