From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Code bloat (was: How Unix brings people together,
Date: Thu, 9 Feb 2017 15:30:05 -0500 [thread overview]
Message-ID: <a730d3b4-fcb7-1304-8344-b0188ef5dad5@kilonet.net> (raw)
In-Reply-To: <20170209195457.373C940B9@lod.com>
WAY off-topic. Sorry.
On 2/9/2017 2:54 PM, Corey Lindsly wrote:
> 3ms? Really? I'm impressed, and I'd like to see your traceroute. We peer
> directly with Google and I get 4-5ms. Do share.
>
>
Two fiber connections here to Verizon FIOS, one business, one residential:
FIOS business fiber 50M/50M in New York, Long Island to be exact, low
4's, high 3's:
root at hnet1:/data/tmp# ping -s 8.8.8.8
PING 8.8.8.8: 56 data bytes
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=0.
time=4.167 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=1.
time=3.871 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=2.
time=4.062 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=3.
time=4.093 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=4.
time=4.050 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=5.
time=3.900 ms
root at hnet1:/data/tmp# traceroute -t 2 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 40 byte packets
1 <removed> (<removed>) 0.598 ms 0.615 ms 0.559 ms
2 B3384.NYCMNY-LCR-22.verizon-gni.net (100.41.217.224) 2.884 ms
3.137 ms 3.903 ms
3 * * *
4 0.ae11.GW13.NYC1.ALTER.NET (140.222.234.191) 2.719 ms
0.ae13.GW13.NYC1.ALTER.NET (140.222.234.193) 2.560 ms
0.ae11.GW13.NYC1.ALTER.NET (140.222.234.191) 2.377 ms
5 google-gw.customer.alter.net (204.148.18.206) 62.332 ms 56.885
ms 55.203 ms
6 209.85.247.33 (209.85.247.33) 2.885 ms 2.771 ms 2.735 ms
7 108.170.233.235 (108.170.233.235) 2.936 ms 108.170.235.13
(108.170.235.13) 3.490 ms 108.170.233.233 (108.170.233.233) 3.152 ms
8 google-public-dns-a.google.com (8.8.8.8) 3.495 ms * *
FIOS residential 150/150M, low 3's:
medusa# ping -s 8.8.8.8
PING 8.8.8.8: 56 data bytes
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=0.
time=3.497 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=1.
time=3.286 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=2.
time=3.368 ms
64 bytes from google-public-dns-a.google.com (8.8.8.8): icmp_seq=3.
time=3.315 ms
Traceroute not available without altering my Cisco ASA config.
I think it's entirely possible that 8.8.8.8 is more than one host, and
depending on geographical location you're being routed to any of a
number of actual hosts ;)
Speed of light from New York to California is approximately 1.3ms. I
can't imagine all these routers don't add SOMETHING to do the latency...
so I can't see how I can ping a California hosts in the low 3 ms area.
next prev parent reply other threads:[~2017-02-09 20:30 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 3:03 [TUHS] How Unix brings people together, or it's a small Doug McIlroy
2017-02-07 4:06 ` Marc Rochkind
2017-02-07 23:10 ` Clem Cole
2017-02-07 23:38 ` Steve Johnson
2017-02-08 2:55 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Greg 'groggy' Lehey
2017-02-08 3:47 ` Nick Downing
2017-02-08 3:56 ` Jason Stevens
2017-02-08 8:25 ` Wesley Parish
2017-02-08 9:57 ` Steve Nickolas
2017-02-08 11:21 ` Nick Downing
2017-02-08 11:59 ` [TUHS] Code bloat (was: How Unix brings people together, or it'sa small...) jsteve
2017-02-08 12:24 ` Nick Downing
2017-02-08 12:29 ` [TUHS] Code bloat Jacob Goense
2017-02-08 12:57 ` Nick Downing
2017-02-08 13:10 ` jsteve
2017-02-08 14:10 ` Jacob Goense
2017-02-08 14:34 ` Ron Natalie
2017-02-08 14:43 ` Brantley Coile
2017-02-08 15:09 ` Dan Cross
2017-02-08 15:26 ` Nick Downing
2017-02-08 15:18 ` Jason Stevens
2017-02-08 16:25 ` Tony Finch
2017-02-09 14:03 ` Jacob Goense
2017-02-09 14:41 ` jsteve
2017-02-09 15:03 ` Jacob Goense
2017-02-09 15:08 ` Jason Stevens
2017-02-09 15:30 ` Tony Finch
2017-02-09 16:14 ` Warner Losh
2017-02-09 23:38 ` [TUHS] Free/NetBSD revision history (was Code bloat) Jacob Goense
2017-02-10 4:11 ` Warner Losh
2017-02-10 4:17 ` Warner Losh
2017-02-08 13:56 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Paul Ruizendaal
[not found] ` <CAH1jEzZqRPYenwzBbUwFVanA-NVvWMGzYiADVoAXCDOqnUrMrg@mail.gmail.com>
2017-02-09 3:02 ` [TUHS] Fwd: " Nick Downing
2017-02-09 9:19 ` [TUHS] " Paul Ruizendaal
2017-02-09 9:58 ` Michael Kjörling
2017-02-09 10:08 ` Paul Ruizendaal
2017-02-09 16:36 ` Larry McVoy
2017-02-09 16:42 ` Warner Losh
2017-02-09 16:49 ` Larry McVoy
2017-02-09 17:24 ` Steffen Nurpmeso
2017-02-09 17:27 ` [TUHS] offtopic: broadband (redirect from bloat) Larry McVoy
2017-02-09 19:05 ` Steffen Nurpmeso
2017-02-09 22:48 ` Joerg Schilling
2017-02-09 19:54 ` [TUHS] Code bloat (was: How Unix brings people together, Corey Lindsly
2017-02-09 20:08 ` pechter
2017-02-09 20:30 ` Arthur Krewat [this message]
2017-02-09 23:47 ` Jacob Goense
2017-02-09 21:06 ` Larry McVoy
2017-02-09 21:02 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Joerg Schilling
2017-02-09 16:58 ` [TUHS] Code bloat William Pechter
2017-02-09 19:50 ` [TUHS] Code bloat (was: How Unix brings people together, or it's a small...) Clem Cole
2017-02-08 5:37 ` Peter Jeremy
2017-02-08 12:16 ` [TUHS] How Unix brings people together, or it's a small ches@Cheswick.com
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a730d3b4-fcb7-1304-8344-b0188ef5dad5@kilonet.net \
--to=krewat@kilonet.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).