WireGuard + Linux Networking Stack Stress Test 1.0.0

system/wireguard-1.0.0 - 20 April 2020 - Initial commit of WireGuard benchmark from Jason Donenfeld.

downloads.xml

<?xml version="1.0"?>
<!--Phoronix Test Suite v9.6.0m3-->
<PhoronixTestSuite>
  <Downloads>
    <Package>
      <URL>http://www.phoronix-test-suite.com/benchmark-files/wireguard-for-pts-1.tar.xz</URL>
      <MD5>aa8fab44253d5e405f6516d1d793db13</MD5>
      <SHA256>6faff58b1a2bd56ad77db3f67a5e09bdabc350fb9cf9fdb0369ca3dadfc4d63a</SHA256>
      <FileName>wireguard-for-pts-1.tar.xz</FileName>
      <FileSize>1724</FileSize>
    </Package>
  </Downloads>
</PhoronixTestSuite>

install.sh

#!/bin/sh

if which iperf3 >/dev/null 2>&1 ;
then
	echo 0 > ~/install-exit-status
else
	echo "ERROR: iperf3 is not found on the system! This test profile needs the 'iperf3' command in the PATH"
	echo 2 > ~/install-exit-status
	exit
fi

if which wg >/dev/null 2>&1 ;
then
	echo 0 > ~/install-exit-status
else
	echo "ERROR: WireGuard is not found on the system! This test profile needs the 'wg' command in the PATH"
	echo 2 > ~/install-exit-status
	exit
fi

tar -xf wireguard-for-pts-1.tar.xz
chmod +x wireguard-for-pts.sh

cat>wireguard<<EOT
#!/bin/sh
./wireguard-for-pts.sh > \$LOG_FILE 2>&1
echo \$? > ~/test-exit-status
EOT
chmod +x wireguard

results-definition.xml

<?xml version="1.0"?>
<!--Phoronix Test Suite v9.6.0m3-->
<PhoronixTestSuite>
  <SystemMonitor>
    <Sensor>sys.time</Sensor>
  </SystemMonitor>
</PhoronixTestSuite>

test-definition.xml

<?xml version="1.0"?>
<!--Phoronix Test Suite v9.6.0m3-->
<PhoronixTestSuite>
  <TestInformation>
    <Title>WireGuard + Linux Networking Stack Stress Test</Title>
    <Description>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.</Description>
    <ResultScale>Seconds</ResultScale>
    <Proportion>LIB</Proportion>
    <TimesToRun>3</TimesToRun>
  </TestInformation>
  <TestProfile>
    <Version>1.0.0</Version>
    <SupportedPlatforms>Linux</SupportedPlatforms>
    <SoftwareType>Benchmark</SoftwareType>
    <TestType>Network</TestType>
    <License>Free</License>
    <Status>Verified</Status>
    <RequiresRoot>TRUE</RequiresRoot>
    <RequiresNetwork>TRUE</RequiresNetwork>
    <EnvironmentSize>1</EnvironmentSize>
    <ProjectURL>https://www.wireguard.com/</ProjectURL>
    <Maintainer>Jason Donenfeld</Maintainer>
    <SystemDependencies>iperf3, wg</SystemDependencies>
  </TestProfile>
</PhoronixTestSuite>