network script should run 1 thread per core

Bug #1468888 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox Provider - Base
Invalid
Medium
Unassigned

Bug Description

INFO:root:Min Transfer speed: 6625.0 mb/s
INFO:root:Max Transfer speed: 7546.0 mb/s
INFO:root:Avg Transfer speed: 6796.347826086957 mb/s
INFO:root:67.96% of theoretical max 10000 Mb/s
WARNING:root:Poor network performance detected
WARNING:root: Transfer speed: 6796.347826086957 mb/s
WARNING:root: 67.96% of theoretical max 10000Mb/s

When run with single thread on some systems with high-bandwidth network interfaces (10Gb+) it's possible that relying on a single CPU thread could bottleneck the results and give potentially unrealisticly low speed measurements. The script output above was from our standard network script execution on a system with a 10GbE NIC.

When run with 8 threads on the same system, the results are more in line with the speed that the card SHOULD be pushing data:

------------------------------------------------------------
Client connecting to 192.168.1.164, TCP port 5001
TCP window size: 256 KByte (WARNING: requested 128 KByte)
------------------------------------------------------------
[ 4] local 192.168.1.149 port 49843 connected with 192.168.1.164 port 5001
[ 5] local 192.168.1.149 port 49844 connected with 192.168.1.164 port 5001
[ 6] local 192.168.1.149 port 49845 connected with 192.168.1.164 port 5001
[ 7] local 192.168.1.149 port 49846 connected with 192.168.1.164 port 5001
[ 8] local 192.168.1.149 port 49847 connected with 192.168.1.164 port 5001
[ 9] local 192.168.1.149 port 49848 connected with 192.168.1.164 port 5001
[ 10] local 192.168.1.149 port 49849 connected with 192.168.1.164 port 5001
[ 3] local 192.168.1.149 port 49842 connected with 192.168.1.164 port 5001
<snip>
[ 3] 0.0-900.0 sec 143 GBytes 1.37 Gbits/sec
[ 4] 0.0-900.0 sec 75.0 GBytes 716 Mbits/sec
[ 5] 0.0-897.0 sec 73.1 GBytes 700 Mbits/sec
[ 6] 0.0-897.0 sec 137 GBytes 1.31 Gbits/sec
[ 7] 0.0-897.0 sec 135 GBytes 1.29 Gbits/sec
[ 8] 0.0-897.0 sec 143 GBytes 1.37 Gbits/sec
[ 9] 0.0-897.0 sec 142 GBytes 1.36 Gbits/sec
[ 10] 0.0-897.0 sec 133 GBytes 1.27 Gbits/sec
[SUM] 0.0-900.0 sec 980 GBytes 9.35 Gbits/sec

Before making any changes, we should verify that this is truly accurate (I believe it is) and modify the network script to run multiple threads (one per core).

It could be ok to modify the script to only do this on 10Gb or faster interfaces as anything less is likely just fine with a single core/thread.

Revision history for this message
Jeff Lane  (bladernr) wrote :

Story created to address this

tags: added: hwcert-server
Changed in plainbox-provider-checkbox:
status: New → Confirmed
status: Confirmed → Triaged
importance: Undecided → Medium
Jeff Lane  (bladernr)
Changed in plainbox-provider-checkbox:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.