Re: [TUHS] Code bloat (was: How Unix brings people together,

WAY off-topic. Sorry. On 2/9/2017 2:54 PM, Corey Lindsly wrote: 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@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@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.