Iperf3 抖动值太高
Iperf3 Jitter Value Way Too High
我是 运行 UDP 测试,我注意到抖动值太高了,是不是 iperf3 源代码中没有正确初始化?客户端和服务器之间的连接非常好。
可能抖动高的原因是prev_transit
没有初始化为零,但我不确定。
抖动应该如何工作:
http://toncar.cz/Tutorials/VoIP/VoIP_Basics_Jitter.html
客户:
[ 4] local 10.131.136.133 port 49402 connected to 10.131.138.232 port 5201
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 16.0 KBytes 131 Kbits/sec 2
[ 4] 1.00-2.00 sec 8.00 KBytes 65.5 Kbits/sec 1
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total
Datagrams [ 4]
0.00-2.00 sec 24.0 KBytes 98.2 Kbits/sec 63.064 ms 0/3 (0%)
[ 4] Sent 3 datagrams
iperf Done.
服务器:
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 0 seconds, 2 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 16.0 KBytes 131 Kbits/sec 67.261 ms 0/2 (0%)
[ 5] 1.00-2.00 sec 8.00 KBytes 65.5 Kbits/sec 63.064 ms 0/1 (0%)
[ 5] 2.00-2.04 sec 0.00 Bytes 0.00 bits/sec 63.064 ms 0/0 (-nan%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-2.04 sec 0.00 Bytes 0.00 bits/sec 63.064 ms 0/3 (0%)
CPU Utilization: local/receiver 0.0% (0.0%u/0.0%s), remote/sender 1.9% (0.3%u/1.8%s)
iperf 3.1
我猜你就是在 iperf3 问题跟踪器中提出这个问题的同一个人,因为这个问题的措辞和问题跟踪器中的措辞几乎相同:
https://github.com/esnet/iperf/issues/672
我在那里回答说每个测量间隔的数据包太少,无法以有意义的方式实际计算抖动。我建议您以更高的比特率发送以获得更多数据点来测量抖动。您还应该使用 3.2 或更高版本的 iperf3,因为发送数据包的时间有所改进。
我是 运行 UDP 测试,我注意到抖动值太高了,是不是 iperf3 源代码中没有正确初始化?客户端和服务器之间的连接非常好。
可能抖动高的原因是prev_transit
没有初始化为零,但我不确定。
抖动应该如何工作: http://toncar.cz/Tutorials/VoIP/VoIP_Basics_Jitter.html
客户:
[ 4] local 10.131.136.133 port 49402 connected to 10.131.138.232 port 5201
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 16.0 KBytes 131 Kbits/sec 2
[ 4] 1.00-2.00 sec 8.00 KBytes 65.5 Kbits/sec 1
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total
Datagrams [ 4]
0.00-2.00 sec 24.0 KBytes 98.2 Kbits/sec 63.064 ms 0/3 (0%)
[ 4] Sent 3 datagrams
iperf Done.
服务器:
Starting Test: protocol: UDP, 1 streams, 8192 byte blocks, omitting 0 seconds, 2 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 16.0 KBytes 131 Kbits/sec 67.261 ms 0/2 (0%)
[ 5] 1.00-2.00 sec 8.00 KBytes 65.5 Kbits/sec 63.064 ms 0/1 (0%)
[ 5] 2.00-2.04 sec 0.00 Bytes 0.00 bits/sec 63.064 ms 0/0 (-nan%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-2.04 sec 0.00 Bytes 0.00 bits/sec 63.064 ms 0/3 (0%)
CPU Utilization: local/receiver 0.0% (0.0%u/0.0%s), remote/sender 1.9% (0.3%u/1.8%s)
iperf 3.1
我猜你就是在 iperf3 问题跟踪器中提出这个问题的同一个人,因为这个问题的措辞和问题跟踪器中的措辞几乎相同:
https://github.com/esnet/iperf/issues/672
我在那里回答说每个测量间隔的数据包太少,无法以有意义的方式实际计算抖动。我建议您以更高的比特率发送以获得更多数据点来测量抖动。您还应该使用 3.2 或更高版本的 iperf3,因为发送数据包的时间有所改进。