You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/virtual-network-test-latency.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,11 @@ ms.author: steveesp
22
22
23
23
# Test VM network latency
24
24
25
-
To achieve the most accurate results, measure your Azure virtual machine (VM) network latency with a tool that's designed for the task. Publicly available tools such as SockPerf (for Linux) and Latte (for Windows) can isolate and measure network latency while excluding other types of latency, such as application latency. These tools focus on the kind of network traffic that affects application performance (namely, Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) traffic).
25
+
To achieve the most accurate results, measure your Azure virtual machine (VM) network latency with a tool that's designed for the task. Publicly available tools such as SockPerf (for Linux) and latte.exe (for Windows) can isolate and measure network latency while excluding other types of latency, such as application latency. These tools focus on the kind of network traffic that affects application performance (namely, Transmission Control Protocol [TCP] and User Datagram Protocol [UDP] traffic).
26
26
27
27
Other common connectivity tools, such as Ping, might measure latency, but their results might not represent the network traffic that's used in real workloads. That's because most of these tools employ the Internet Control Message Protocol (ICMP), which can be treated differently from application traffic and whose results might not apply to workloads that use TCP and UDP.
28
28
29
-
For accurate network latency testing of the protocols used by most applications, SockPerf (for Linux) and Latte (for Windows) produce the most relevant results. This article covers both of these tools.
29
+
For accurate network latency testing of the protocols used by most applications, SockPerf (for Linux) and latte.exe (for Windows) produce the most relevant results. This article covers both of these tools.
30
30
31
31
## Overview
32
32
@@ -107,7 +107,7 @@ For example, if you copied latte.exe to the *c:\tools* folder, this would be the
107
107
* On the *sender*, start latte.exe (run it from the CMD window, not from PowerShell):
108
108
109
109
```cmd
110
-
latte -c -a \<Receiver IP address\>:\<port\> -i \<iterations\>
110
+
latte -c -a <Receiver IP address>:<port> -i <iterations>
111
111
```
112
112
113
113
The resulting command is the same as on the receiver, except with the addition of *-c* to indicate that this is the *client*, or *sender*:
@@ -122,14 +122,14 @@ To test VMs that are running Linux, use [SockPerf](https://github.com/mellanox/s
122
122
123
123
### Install SockPerf on the VMs
124
124
125
-
On the Linux VMs, both *sender* and *receiver*, run the following commands to prepare SockPerf on the VMs. Commands are provided for the major distros.
125
+
On the Linux VMs, both *sender* and *receiver*, run the following commands to prepare SockPerf on the VMs. Commands are provided for the major distros.
126
126
127
127
#### For Red Hat Enterprise Linux (RHEL)/CentOS
128
128
129
129
Run the following commands:
130
130
131
131
```bash
132
-
#CentOS / RHEL - Install Git and other helpful tools
132
+
#CentOS/RHEL - Install Git and other helpful tools
133
133
sudo yum install gcc -y -q
134
134
sudo yum install git -y -q
135
135
sudo yum install gcc-c++ -y
@@ -171,7 +171,7 @@ make
171
171
sudo make install
172
172
```
173
173
174
-
### Run SockPerf on the VMs
174
+
### Run SockPerf on the VMs
175
175
176
176
After the SockPerf installation is complete, the VMs are ready to run the latency tests.
177
177
@@ -202,4 +202,4 @@ This SockPerf example uses a 350-byte message size, which is typical for an aver
202
202
* Improve latency with an [Azure proximity placement group](https://docs.microsoft.com/azure/virtual-machines/linux/co-location).
203
203
* Learn how to [Optimize networking for VMs](../virtual-network/virtual-network-optimize-network-bandwidth.md) for your scenario.
204
204
* Read about [how bandwidth is allocated to virtual machines](../virtual-network/virtual-machine-network-throughput.md).
205
-
* For more information, see [Azure Virtual Network FAQ](../virtual-network/virtual-networks-faq.md).
205
+
* For more information, see [Azure Virtual Network FAQ](../virtual-network/virtual-networks-faq.md).
0 commit comments