Flent-users discussion archives
 help / color / mirror / Atom feed
From: Rich Brown <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] flent: extremely high ping times on macOS (#178)
Date: Mon, 09 Sep 2019 08:10:11 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/178/529523344@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/178@github.com>


[-- Attachment #1.1: Type: text/plain, Size: 3514 bytes --]

> > 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 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 or view it on GitHub:
https://github.com/tohojo/flent/issues/178#issuecomment-529523344

[-- Attachment #1.2: Type: text/html, Size: 5046 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

  parent reply	other threads:[~2019-09-09 15:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 11:57 Rich Brown
2019-09-06 14:49 ` Dave Täht
2019-09-06 15:15 ` Rich Brown
2019-09-06 17:58 ` Toke Høiland-Jørgensen
2019-09-06 18:58 ` Rich Brown
2019-09-06 22:46 ` Toke Høiland-Jørgensen
2019-09-08 22:33 ` Rich Brown
2019-09-08 23:04 ` Toke Høiland-Jørgensen
2019-09-09  0:06 ` Rich Brown
2019-09-09 12:25 ` Toke Høiland-Jørgensen
2019-09-09 15:07 ` Rich Brown
2019-09-09 15:10 ` Rich Brown [this message]
2019-09-09 15:13 ` Rich Brown
2019-09-09 17:00 ` Toke Høiland-Jørgensen
2019-09-09 17:01 ` Toke Høiland-Jørgensen
2019-09-11 16:31 ` Toke Høiland-Jørgensen
2019-09-12 12:26 ` Rich Brown
2019-09-12 12:26 ` Rich Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tohojo/flent/issues/178/529523344@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP4OPWDJ3FU6M7GGZ6F3QOV6HEVBNHHB2OJTQQ@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] flent: extremely high ping times on macOS (#178)' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox