network.test

network

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2403292-NE-NETWORKTE30
Jump To Table - Results

Statistics

Remove Outliers Before Calculating Averages

Graph Settings

Prefer Vertical Bar Graphs

Multi-Way Comparison

Condense Multi-Option Tests Into Single Result Graphs

Table

Show Detailed System Result Table

Run Management

Result
Identifier
Performance Per
Dollar
Date
Run
  Test
  Duration
network.txt
March 29
  14 Minutes
Only show results matching title/arguments (delimit multiple options with a comma):
Do not show results matching title/arguments (delimit multiple options with a comma):


network.testOpenBenchmarking.orgPhoronix Test Suite2 x Intel Xeon Platinum 8480+ @ 3.80GHz (112 Cores / 224 Threads)American Megatrends LLC. T3DGQ01.00Intel Device 1bce4 x 32 GB 4800MT/s4001GB Seagate ST4000VX016-3CV1 + 1600GB INTEL SSDSC2BX01 + 31GB Flash DiskASPEEDDELL 1708FP2 x Intel I210Ubuntu 20.045.4.0-174-generic (x86_64)GCC 9.4.0ext41280x1024ProcessorMotherboardChipsetMemoryDiskGraphicsMonitorNetworkOSKernelCompilerFile-SystemScreen ResolutionNetwork.test BenchmarksSystem Logs- Transparent Huge Pages: madvise- --build=x86_64-linux-gnu --disable-vtable-verify --disable-werror --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-gnu-unique-object --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-multiarch --enable-multilib --enable-nls --enable-objc-gc=auto --enable-offload-targets=nvptx-none=/build/gcc-9-9QDOt0/gcc-9-9.4.0/debian/tmp-nvptx/usr,hsa --enable-plugin --enable-shared --enable-threads=posix --host=x86_64-linux-gnu --program-prefix=x86_64-linux-gnu- --target=x86_64-linux-gnu --with-abi=m64 --with-arch-32=i686 --with-default-libstdcxx-abi=new --with-gcc-major-version-only --with-multilib-list=m32,m64,mx32 --with-target-system-zlib=auto --with-tune=generic --without-cuda-driver -v - Scaling Governor: intel_pstate powersave (EPP: balance_performance) - CPU Microcode: 0x2b000571- gather_data_sampling: Not affected + itlb_multihit: Not affected + l1tf: Not affected + mds: Not affected + meltdown: Not affected + mmio_stale_data: Not affected + retbleed: Not affected + 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 Enhanced IBRS IBPB: conditional RSB filling PBRSB-eIBRS: SW sequence + srbds: Not affected + tsx_async_abort: Not affected

network.testsockperf: Throughputsockperf: Latency Ping Pongsockperf: Latency Under Loadnetperf: UDP Stream - Server To Client - 10G - 10 Secondsnetwork.txt21180812.58914.724OpenBenchmarking.org

Sockperf

This is a network socket API performance benchmark. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgMessages Per Second, More Is BetterSockperf 3.4Test: Throughputnetwork.txt50K100K150K200K250KSE +/- 6399.03, N = 252118081. (CXX) g++ options: --param -O3 -rdynamic -ldl -lpthread

OpenBenchmarking.orgusec, Fewer Is BetterSockperf 3.4Test: Latency Ping Pongnetwork.txt3691215SE +/- 0.30, N = 2512.591. (CXX) g++ options: --param -O3 -rdynamic -ldl -lpthread

OpenBenchmarking.orgusec, Fewer Is BetterSockperf 3.4Test: Latency Under Loadnetwork.txt48121620SE +/- 0.60, N = 2514.721. (CXX) g++ options: --param -O3 -rdynamic -ldl -lpthread

Ethr

Ethr is a cross-platform Golang-written network performance measurement tool developed by Microsoft that is capable of testing multiple protocols and different measurements. Learn more via the OpenBenchmarking.org test page.

Server Address: localhost - Protocol: TCP - Test: Latency - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: UDP - Test: Latency - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: HTTP - Test: Latency - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: TCP - Test: Bandwidth - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: UDP - Test: Bandwidth - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: HTTP - Test: Bandwidth - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: TCP - Test: Connections/s - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: UDP - Test: Connections/s - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

Server Address: localhost - Protocol: HTTP - Test: Connections/s - Threads: 1

network.txt: The test run did not produce a result. The test run did not produce a result. The test run did not produce a result. E: ./ethr: 5: ./ethr: not found

iPerf

iPerf is a network bandwidth throughput testing software. This test profile is used for automated testing of an iperf client and requires you have access to an iperf server. Learn more via the OpenBenchmarking.org test page.

Server Address: localhost - Server Port: 5555 - Duration: 10 Seconds - Test: UDP - 100Mbit Objective - Parallel: 20

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: iperf3: error - unable to connect to server: Connection refused

Server Address: localhost - Server Port: 5555 - Duration: 10 Seconds - Test: UDP - 1000Mbit Objective - Parallel: 20

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: iperf3: error - unable to connect to server: Connection refused

Server Address: localhost - Server Port: 5555 - Duration: 10 Seconds - Test: TCP - Parallel: 20

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: iperf3: error - unable to connect to server: Connection refused

Server Address: localhost - Server Port: 5555 - Duration: 10 Seconds - Test: UDP - Parallel: 20

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status. E: iperf3: error - unable to connect to server: Connection refused

Netperf

Netperf is a network bandwidth testing software. This test profile is used for automated testing of a netperf client and requires you have access to a netperf server. Learn more via the OpenBenchmarking.org test page.

Server: localhost - Test: TCP Send File - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

Server: localhost - Test: TCP Request Response - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

Server: localhost - Test: UDP Request Response - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

Server: localhost - Test: TCP Stream - Client To Server - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

Server: localhost - Test: TCP Stream - Server To Client - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.

Server: localhost - Test: UDP Stream - Server To Client - 10G - Duration: 10 Seconds

network.txt: The test quit with a non-zero exit status. The test quit with a non-zero exit status. The test quit with a non-zero exit status.