[ovs-build] Passed: yyang13/ovs#28 (master - 83b5e8f)
Travis CI
builds at travis-ci.org
Thu Oct 22 09:40:35 UTC 2020
Build Update for yyang13/ovs
-------------------------------------
Build: #28
Status: Passed
Duration: 1 hr, 9 mins, and 33 secs
Commit: 83b5e8f (master)
Author: Yi Yang
Message: userspace: fix bad UDP performance issue of veth
iperf3 UDP performance of veth to veth case is
very very bad because of too many packet loss,
the root cause is rmem_default and wmem_default
are just 212992, but iperf3 UDP test used 8K
UDP size which resulted in many UDP fragment in
case that MTU size is 1500, one 8K UDP send would
enqueue 6 UDP fragments to socket receive queue,
the default small socket buffer size can't cache
so many packets that many packets are lost.
This commit fixed packet loss issue, it allows
users to set socket receive and send buffer size
per their own system environment to proper value,
therefore there will not be packet loss.
Users can set system interface socket buffer size
by command lines:
$ sudo sh -c "echo 1073741823 > /proc/sys/net/core/wmem_max"
$ sudo sh -c "echo 1073741823 > /proc/sys/net/core/rmem_max"
or
$ sudo ovs-vsctl set Open_vSwitch . \
other_config:userspace-sock-buf-size=1073741823
But final socket buffer size is minimum one among of them.
Possible value range is 212992 to 1073741823. Users must
explicitly set other_config:userspace-sock-buf-size to the
value they expect, otherwise OVS won't set socket send
and receive buffer size. More details about it is in the
document
Documentation/howto/userspace-udp-performance-tunning.rst.
By the way, big socket buffer doesn't mean it will
allocate big buffer on creating socket, actually
it won't alocate any extra buffer compared to default
socket buffer size, it just means more skbuffs can
be enqueued to socket receive queue and send queue,
therefore there will not be packet loss.
The below is for your reference.
The result before apply this commit
===================================
$ ip netns exec ns02 iperf3 -t 5 -i 1 -u -b 100M -c 10.15.2.6 --get-server-output -A 5
Connecting to host 10.15.2.6, port 5201
[ 4] local 10.15.2.2 port 59053 connected to 10.15.2.6 port 5201
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 10.8 MBytes 90.3 Mbits/sec 1378
[ 4] 1.00-2.00 sec 11.9 MBytes 100 Mbits/sec 1526
[ 4] 2.00-3.00 sec 11.9 MBytes 100 Mbits/sec 1526
[ 4] 3.00-4.00 sec 11.9 MBytes 100 Mbits/sec 1526
[ 4] 4.00-5.00 sec 11.9 MBytes 100 Mbits/sec 1526
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-5.00 sec 58.5 MBytes 98.1 Mbits/sec 0.047 ms 357/531 (67%)
[ 4] Sent 531 datagrams
Server output:
-----------------------------------------------------------
Accepted connection from 10.15.2.2, port 60314
[ 5] local 10.15.2.6 port 5201 connected to 10.15.2.2 port 59053
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 1.36 MBytes 11.4 Mbits/sec 0.047 ms 357/531 (67%)
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 0.047 ms 0/0 (-nan%)
[ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0.047 ms 0/0 (-nan%)
[ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 0.047 ms 0/0 (-nan%)
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0.047 ms 0/0 (-nan%)
iperf Done.
The result after apply this commit
===================================
$ sudo ip netns exec ns02 iperf3 -t 5 -i 1 -u -b 4G -c 10.15.2.6 --get-server-output -A 5
Connecting to host 10.15.2.6, port 5201
[ 4] local 10.15.2.2 port 48547 connected to 10.15.2.6 port 5201
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 440 MBytes 3.69 Gbits/sec 56276
[ 4] 1.00-2.00 sec 481 MBytes 4.04 Gbits/sec 61579
[ 4] 2.00-3.00 sec 474 MBytes 3.98 Gbits/sec 60678
[ 4] 3.00-4.00 sec 480 MBytes 4.03 Gbits/sec 61452
[ 4] 4.00-5.00 sec 480 MBytes 4.03 Gbits/sec 61441
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-5.00 sec 2.30 GBytes 3.95 Gbits/sec 0.024 ms 0/301426 (0%)
[ 4] Sent 301426 datagrams
Server output:
-----------------------------------------------------------
Accepted connection from 10.15.2.2, port 60320
[ 5] local 10.15.2.6 port 5201 connected to 10.15.2.2 port 48547
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 209 MBytes 1.75 Gbits/sec 0.021 ms 0/26704 (0%)
[ 5] 1.00-2.00 sec 258 MBytes 2.16 Gbits/sec 0.025 ms 0/32967 (0%)
[ 5] 2.00-3.00 sec 258 MBytes 2.16 Gbits/sec 0.022 ms 0/32987 (0%)
[ 5] 3.00-4.00 sec 257 MBytes 2.16 Gbits/sec 0.023 ms 0/32954 (0%)
[ 5] 4.00-5.00 sec 257 MBytes 2.16 Gbits/sec 0.021 ms 0/32937 (0%)
[ 5] 5.00-6.00 sec 255 MBytes 2.14 Gbits/sec 0.026 ms 0/32685 (0%)
[ 5] 6.00-7.00 sec 254 MBytes 2.13 Gbits/sec 0.025 ms 0/32453 (0%)
[ 5] 7.00-8.00 sec 255 MBytes 2.14 Gbits/sec 0.026 ms 0/32679 (0%)
[ 5] 8.00-9.00 sec 255 MBytes 2.14 Gbits/sec 0.022 ms 0/32669 (0%)
iperf Done.
Signed-off-by: Yi Yang <yangyi01 at inspur.com>
View the changeset: https://github.com/yyang13/ovs/compare/182a28a5599c...83b5e8ffdcaa
View the full build log and details: https://travis-ci.org/github/yyang13/ovs/builds/737956946?utm_medium=notification&utm_source=email
--
You can unsubscribe from build emails from the yyang13/ovs repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=27957055&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-build/attachments/20201022/b1ffa6ed/attachment-0001.html>
More information about the build
mailing list