Closed #178.
--
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#event-2628972439___
Flent-users mailing list
Flent-users@flent.org
I am going to close this for now. Two reasons:
1. The primary reason for this report was that I misunderstood how Flent
measures latency for its default plot. Currently, that plot shows latency to
the -H host. As noted in
https://github.com/tohojo/flent/issues/181#issuecomment-530500478, there
Rich Brown writes:
> Update: I'm trying to get repeatable test showing a difference of latency
> between the Flent ping_host values and a separate/concurrent fping run. (I
> saw it two days ago, but can't reproduce now... This is roundabout way to say
> that, for the moment, the Flent
Update: I'm trying to get repeatable test showing a difference of latency
between the Flent ping_host values and a separate/concurrent fping run. (I saw
it two days ago, but can't reproduce now... This is roundabout way to say that,
for the moment, the Flent ping_host and separate fping runs
Rich Brown writes:
>> > 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)?
>
>> Good question. IPv4 vs IPv6 maybe?
>
> I don't
PS Why am I perseverating about this now? I have taken Dave's script and
packaged it for ease of use. See [Coffee Shop Bloat
Script](https://github.com/richb-hanover/coffee-shop-bloat-test)
I can conceal a lot of the options into the script if I know what they are.
Thanks again.
--
You are
> > 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)?
> Good question. IPv4 vs IPv6 maybe?
I don't think so. Here's fping for both
> > 1. Could flent charts use the `--test-parameter=ping_hosts=...` instead of
> > values from the -H host?
> Well, it should probably show both by default. For now, there's a separate
> plot type you can use to see the extra flows (-p ping_extra).
I don't see how to use the `-p` option. When
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
Rich Brown writes:
> Ahah! I see the difference. I was testing against `gstatic.com` with
> Terminal; Flent was testing against `flent-fremont.bufferbloat.net`
>
> This seems a pretty big disparity between test results. Is there an
> option to tell Flent to ping a more local host? Thanks.
You
Ahah! I see the difference. I was testing against `gstatic.com` with Terminal;
Flent was testing against `flent-fremont.bufferbloat.net`
This seems a pretty big disparity between test results. Is there an option to
tell Flent to ping a more local host? Thanks.
```
bash-3.2$ fping -c 1000
Rich Brown writes:
> Here's the log file: https://pastebin.com/aBXCgjD1
>
> NB I'll be away for the weekend, so won't follow up for a while.
> Thanks.
Looks like those are the actual ping times reported by fping:
[1567795827.309700] flent-fremont.bufferbloat.net : [175], 84 bytes, 95.5 ms
Here's the log file: https://pastebin.com/aBXCgjD1
NB I'll be away for the weekend, so won't follow up for a while. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Rich Brown writes:
> Hmmm, not this time... What else could I check?
>
> 
If you turn on debug logging during the test run (-L option), that log
will include the actual output of the
Hmmm, not this time... What else could I check?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
15 matches
Mail list logo
