Rich Brown <notifications@github.com> writes:
> Using Flent 1.3.0 with fping 4.2 on macOS 10.2.6:
>
> I see high ping times (>100 msec in the following report) despite the
> fact that actual ping times (measured by fping during the flent test)
> are 20-30 msec, and none higher that 47 msec. (I am on 7mbps/768kbps
> DSL, so the 6.95mbps seems accurate.)
>
> Here is the data file.
> tcp_ndown-2019-09-06T074544.888052.Rich_Test.flent.gz
>
> What other information could I provide? Thanks.
>
> bash-3.2$ flent -x -H flent-fremont.bufferbloat.net -t "Rich_Test" --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-06T074544.888052.Rich_Test.flent.gz.
>
> Summary of tcp_ndown test run from 2019-09-06 11:45:44.888052
> Title: 'Rich_Test'
>
> avg median # data pts
> Ping (ms) ICMP : 104.03 105.00 ms 350
I have seen this statistic be wildly wrong in the summary but correct in
the graph.
> TCP download avg : 1.71 1.74 Mbits/s 300
> TCP download sum : 6.83 6.95 Mbits/s 300
> TCP download::1 : 1.55 1.56 Mbits/s 281
> TCP download::2 : 1.85 1.83 Mbits/s 282
> TCP download::3 : 1.53 1.54 Mbits/s 282
> TCP download::4 : 1.91 1.90 Mbits/s 287
> bash-3.2$
> bash-3.2$ fping --version
> fping: Version 4.2
> fping: comments to david@schweikert.ch
>
> bash-3.2$ fping -c 1000 gstatic.com -D
> [1567770338.594778] gstatic.com : [0], 84 bytes, 20.7 ms (20.7 avg, 0% loss)
> [1567770339.600662] gstatic.com : [1], 84 bytes, 21.7 ms (21.2 avg, 0% loss)
> [1567770340.602339] gstatic.com : [2], 84 bytes, 21.5 ms (21.3 avg, 0% loss)
> [1567770341.605205] gstatic.com : [3], 84 bytes, 22.2 ms (21.5 avg, 0% loss)
> [1567770342.608899] gstatic.com : [4], 84 bytes, 21.0 ms (21.4 avg, 0% loss)
> [1567770343.613397] gstatic.com : [5], 84 bytes, 21.4 ms (21.4 avg, 0% loss)
> [1567770344.618612] gstatic.com : [6], 84 bytes, 21.5 ms (21.4 avg, 0% loss)
> [1567770345.618789] gstatic.com : [7], 84 bytes, 20.8 ms (21.3 avg, 0% loss)
> ...
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.