Avoid using atomic primitives in the hot path

NTTTCP-for-Linux

Summary

A multiple-threaded Linux network throughput benchmark tool.

Features

Multiple threads to send/receive data ('-P', '-n', and '-l'). By default, Receiver ('-r') uses 16 threads and Sender ('-s') uses 64 threads to exchange data.
Support cpu affinity ('-m').
Support running in background (daemon, '-D').
Support Sender and Receiver sync mode by default. Use "-N" (no_sync) to disable the sync.
Support testing with multiple clients mode (use '-M' on Receiver, and '-L' on the last Sender).
Support select() by default, and epoll() (use '-e' on Receiver).
Support both TCP (by default), and UDP ('-u') tests.
Support pin TCP server or client port (use '-p' on Receiver or '-f' on Sender).
Support test Warmup ('-W') and Cooldown ('-C').
Support reporting TCP retransmit ('--show-tcp-retrans').
Support reporting number of packets ('--show-nic-packets') and number of interrupts ('--show-dev-interrupts').
Support bandwidth limit ('-B' or '--fq-rate-limit').
Support capturing console log to file ('-O').
Support writing log into XML file ('-x').
Support writing log into JSON file ('-j').

Getting Started

Building NTTTCP-for-Linux

Using make:

	make; make install

Using CMake:

	cd src
	mkdir build && cd build
	cmake ..
	make && make install

Usage

ntttcp -h

Known issues

Example run

To measure the network performance between two multi-core serves running SLES 12, NODE1 (192.168.4.1) and NODE2 (192.168.4.2), connected via a 40 GigE connection.

On NODE1 (the receiver), run:

./ntttcp -r

(Translation: Run ntttcp as a receiver with default setting. The default setting includes: with 16 threads created and run across all CPUs, allocating 64K receiver buffer, and run for 60 seconds.)

And on NODE2 (the sender), run:

./ntttcp -s192.168.4.1

(Translation: Run ntttcp as a sender, with default setting. The default setting includes: with 64 threads created and run across all CPUs, allocating 128KB sender buffer, and run for 60 seconds.)

Using the above parameters, the program returns results on both the sender and receiver nodes, correlating network communication to CPU utilization.

Example receiver-side output from a given run (which showcases 37.66 Gbps throughput):

NODE1:/home/simonxiaoss/ntttcp-for-linux/src # ./ntttcp -s 10.0.0.1 -W 1 -t 10 -C 1
NTTTCP for Linux 1.3.4
---------------------------------------------------------
22:36:30 INFO: Network activity progressing...
22:36:30 INFO: 64 threads created
22:36:31 INFO: Test warmup completed.
22:36:42 INFO: Test run completed.
22:36:42 INFO: 64 connections tested
22:36:42 INFO: #####  Totals:  #####
22:36:42 INFO: test duration    :10.36 seconds
22:36:42 INFO: total bytes      :30629953536
22:36:42 INFO:   throughput     :23.65Gbps
22:36:42 INFO: cpu cores        :20
22:36:42 INFO:   cpu speed      :2394.455MHz
22:36:42 INFO:   user           :3.60%
22:36:42 INFO:   system         :3.44%
22:36:42 INFO:   idle           :91.57%
22:36:42 INFO:   iowait         :0.00%
22:36:42 INFO:   softirq        :1.38%
22:36:42 INFO:   cycles/byte    :1.37
22:36:42 INFO: cpu busy (all)   :159.81%
---------------------------------------------------------
22:40:52 INFO: Test cooldown is in progress...
22:40:52 INFO: Test cycle finished.

Related topics

Terms of Use

By downloading and running this project, you agree to the license terms of the third party application software, Microsoft products, and components to be installed.

The third party software and products are provided to you by third parties. You are responsible for reading and accepting the relevant license terms for all software that will be installed. Microsoft grants you no rights to third party software.

License

The MIT License (MIT)

Copyright (c) 2015 Microsoft Corporation

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

microsoft / ntttcp-for-linux Goto Github PK

ntttcp-for-linux's Introduction

NTTTCP-for-Linux

Summary

Features

Getting Started

Building NTTTCP-for-Linux

Usage

Known issues

Example run

Related topics

Terms of Use

License

ntttcp-for-linux's People

Contributors

Stargazers

Watchers

Forkers

ntttcp-for-linux's Issues

17:06:13 INFO: the UDP send size is too big. use the max value 17:06:13 INFO: 17 threads created NTTTCP for Linux 1.4.0

---------------- Receiver ------------------ ntttcp -r -V --show-tcp-retrans --show-nic-packets wlan0 -p 6051 -t 86400 < NTTTCP for Linux 1.4.0

-------------------Sender -------------------- ntttcp -s 10.231.111.166 -V --show-tcp-retrans --show-nic-packets wlan0 -p 6051 -t 86400 < NTTTCP for Linux 1.4.0

windows_x86_64:/data/local/tmp/test $ ./ntttcp -r -m 1,*,10.231.111.24 -V -p 8011 -t 86400 -u -b 1024 NTTTCP for Linux 1.4.0

1|windows_x86_64:/data/local/tmp/test $ ./ntttcp -s -m 1,*,10.231.111.24 -V -p 8011 -t 86400 -u -n 1 -b 1024 NTTTCP for Linux 1.4.0

/opt/ntttcp-for-linux/src> ./ntttcp -r -V NTTTCP for Linux 1.2.0

*** receiver role threads: 16 cpu affinity: * server address: 0.0.0.0 domain: IPv4 protocol: TCP server port starting at: 5001 receiver socket buffer (bytes): 65536 test duration (sec): 60 show system tcp retransmit: no verbose mode: enabled

using Single Thread: /opt/ntttcp-for-linux/src> ./ntttcp -r -m 1 -V NTTTCP for Linux 1.2.0

*** receiver role threads: 1 cpu affinity: * server address: 0.0.0.0 domain: IPv4 protocol: TCP server port starting at: 5001 receiver socket buffer (bytes): 65536 test duration (sec): 60 show system tcp retransmit: no verbose mode: enabled

Recommend Projects

Recommend Topics

Recommend Org

17:06:13 INFO: the UDP send size is too big. use the max value
17:06:13 INFO: 17 threads created
NTTTCP for Linux 1.4.0

---------------- Receiver ------------------
ntttcp -r -V --show-tcp-retrans --show-nic-packets wlan0 -p 6051 -t 86400 <
NTTTCP for Linux 1.4.0

-------------------Sender --------------------
ntttcp -s 10.231.111.166 -V --show-tcp-retrans --show-nic-packets wlan0 -p 6051 -t 86400 <
NTTTCP for Linux 1.4.0

windows_x86_64:/data/local/tmp/test $ ./ntttcp -r -m 1,*,10.231.111.24 -V -p 8011 -t 86400 -u -b 1024
NTTTCP for Linux 1.4.0

1|windows_x86_64:/data/local/tmp/test $ ./ntttcp -s -m 1,*,10.231.111.24 -V -p 8011 -t 86400 -u -n 1 -b 1024
NTTTCP for Linux 1.4.0

/opt/ntttcp-for-linux/src> ./ntttcp -r -V
NTTTCP for Linux 1.2.0

*** receiver role
threads: 16
cpu affinity: *
server address: 0.0.0.0
domain: IPv4
protocol: TCP
server port starting at: 5001
receiver socket buffer (bytes): 65536
test duration (sec): 60
show system tcp retransmit: no
verbose mode: enabled

using Single Thread:
/opt/ntttcp-for-linux/src> ./ntttcp -r -m 1 -V
NTTTCP for Linux 1.2.0

*** receiver role
threads: 1
cpu affinity: *
server address: 0.0.0.0
domain: IPv4
protocol: TCP
server port starting at: 5001
receiver socket buffer (bytes): 65536
test duration (sec): 60
show system tcp retransmit: no
verbose mode: enabled