Hmmm... The `--test-parameter=ping_hosts=gstatic.com` information appears in the command-line summary but not in the charts. Is this correct?

If so, the charts display significantly different latency depending on which -H host gets used.  The Terminal display (bottom) shows fairly consistent ping times and transfer rate measurements using either of the two hosts.

This raises two questions:

1. Could flent charts use the `--test-parameter=ping_hosts=...` instead of values from the -H host? 

2. 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)?

Thanks.

**Test to flent-fremont.bufferbloat.net gives latency > 100 msec:**
<img width="586" alt="image" src="https://user-images.githubusercontent.com/1094930/64496066-28d8a400-d26f-11e9-89ea-8b1a03b69872.png">

**Test to netperf.bufferbloat.net gives latency 55-65 msec:**
<img width="586" alt="image" src="https://user-images.githubusercontent.com/1094930/64496060-1d857880-d26f-11e9-9793-a36c7e0b0423.png">

**Text summary from flent-fremont.bufferbloat.net:**
```
bash-3.2$ flent -x -H flent-fremont.bufferbloat.net -t "Rich_Test" --test-parameter=ping_hosts=gstatic.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-08T193622.518606.Rich_Test.flent.gz.

Summary of tcp_ndown test run from 2019-09-08 23:36:22.518606
  Title: 'Rich_Test'

                                               avg       median          # data pts
 Ping (ms) ICMP                     :       104.28       105.00 ms              350
 Ping (ms) ICMP gstatic.com (extra) :        33.10        33.65 ms              350
 TCP download avg                   :         1.72         1.74 Mbits/s         301
 TCP download sum                   :         6.87         6.95 Mbits/s         301
 TCP download::1                    :         1.72         1.68 Mbits/s         285
 TCP download::2                    :         1.85         1.77 Mbits/s         287
 TCP download::3                    :         1.62         1.61 Mbits/s         284
 TCP download::4                    :         1.70         1.70 Mbits/s         283
bash-3.2$
```

**Text summary from netperf.bufferbloat.net:**
```
bash-3.2$ flent -x -H netperf.bufferbloat.net -t "netperf.bufferbloat.net" --test-parameter=ping_hosts=gstatic.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-08T194842.664611.netperf_bufferbloat_net.flent.gz.

Summary of tcp_ndown test run from 2019-09-08 23:48:42.664611
  Title: 'netperf.bufferbloat.net'

                                               avg       median          # data pts
 Ping (ms) ICMP                     :        54.51        56.30 ms              349
 Ping (ms) ICMP gstatic.com (extra) :        35.73        38.00 ms              349
 TCP download avg                   :         1.73         1.74 Mbits/s         300
 TCP download sum                   :         6.92         6.95 Mbits/s         300
 TCP download::1                    :         2.40         2.28 Mbits/s         279
 TCP download::2                    :         1.19         1.09 Mbits/s         259
 TCP download::3                    :         2.47         2.32 Mbits/s         278
 TCP download::4                    :         0.96         0.92 Mbits/s         253
bash-3.2$
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/178#issuecomment-529258895