- Why is there a discrepency between the
--test-parameter=ping_hosts=...
reading (showing 30-38 msec in my
tests) and a separate, concurrent fping test (see original post, where
it was running 20-22 msec)?
Good question. IPv4 vs IPv6 maybe?
I don't think so. Here's fping for both atl.richb-hanover.com (IPv4 only) and atl6 (IPv6)...
bash-3.2$ fping -c 1000 atl.richb-hanover.com -D
[1568033075.420184] atl.richb-hanover.com : [0], 84 bytes, 40.4 ms (40.4 avg, 0% loss)
[1568033076.423893] atl.richb-hanover.com : [1], 84 bytes, 40.9 ms (40.6 avg, 0% loss)
[1568033077.426595] atl.richb-hanover.com : [2], 84 bytes, 41.7 ms (41.0 avg, 0% loss)
[1568033078.430768] atl.richb-hanover.com : [3], 84 bytes, 40.8 ms (40.9 avg, 0% loss)
^C
bash-3.2$ fping -c 1000 atl6.richb-hanover.com -D -6
[1568033063.252647] atl6.richb-hanover.com : [0], 64 bytes, 40.0 ms (40.0 avg, 0% loss)
[1568033064.254237] atl6.richb-hanover.com : [1], 64 bytes, 40.8 ms (40.4 avg, 0% loss)
[1568033065.257423] atl6.richb-hanover.com : [2], 64 bytes, 40.7 ms (40.5 avg, 0% loss)
[1568033066.261700] atl6.richb-hanover.com : [3], 64 bytes, 40.8 ms (40.6 avg, 0% loss)
^C
atl6.richb-hanover.com : xmt/rcv/%loss = 4/4/0%, min/avg/max = 40.0/40.6/40.8
And the results using atl.richb-hanover.com for the Flent: 54.77 msec during the test with 40-ish msec readings from fping and ping immediately thereafter.
bash-3.2$ flent -x -H atl.richb-hanover.com -t "atl.richb-hanover.com" --te=download_streams=4 tcp_ndown
Started Flent 1.3.0 using Python 2.7.15.
Starting tcp_ndown test. Expected run time: 70 seconds.
Data file written to ./tcp_ndown-2019-09-09T110116.988820.atl_richb-hanover_com.flent.gz.
Summary of tcp_ndown test run from 2019-09-09 15:01:16.988820
Title: 'atl.richb-hanover.com'
avg median # data pts
Ping (ms) ICMP : 54.77 57.05 ms 350
TCP download avg : 1.73 1.74 Mbits/s 300
TCP download sum : 6.94 6.96 Mbits/s 300
TCP download::1 : 2.09 2.02 Mbits/s 274
TCP download::2 : 1.56 1.44 Mbits/s 268
TCP download::3 : 0.99 0.90 Mbits/s 251
TCP download::4 : 2.39 2.31 Mbits/s 278
bash-3.2$ fping -D atl.richb-hanover.com -c 4
[1568041403.319308] atl.richb-hanover.com : [0], 84 bytes, 52.5 ms (52.5 avg, 0% loss)
[1568041404.312934] atl.richb-hanover.com : [1], 84 bytes, 41.0 ms (46.7 avg, 0% loss)
[1568041405.313312] atl.richb-hanover.com : [2], 84 bytes, 40.7 ms (44.7 avg, 0% loss)
[1568041406.318130] atl.richb-hanover.com : [3], 84 bytes, 40.9 ms (43.8 avg, 0% loss)
atl.richb-hanover.com : xmt/rcv/%loss = 4/4/0%, min/avg/max = 40.7/43.8/52.5
bash-3.2$ ping atl.richb-hanover.com
PING atl.richb-hanover.com (23.226.232.80): 56 data bytes
64 bytes from 23.226.232.80: icmp_seq=0 ttl=51 time=40.722 ms
64 bytes from 23.226.232.80: icmp_seq=1 ttl=51 time=41.313 ms
64 bytes from 23.226.232.80: icmp_seq=2 ttl=51 time=41.022 ms
64 bytes from 23.226.232.80: icmp_seq=3 ttl=51 time=40.871 ms
^C
--- atl.richb-hanover.com ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 40.722/40.982/41.313/0.219 ms
bash-3.2$```
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.