我的情况之一就是遇到了一些不寻常的问题。对任何站点执行Ping操作极其缓慢。尝试保持SSH连接也很糟糕。
以下是对yahoo的ping操作。知道是什么原因造成的吗？
PING yahoo.com (98.139.183.24) 56(84) bytes of data. 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=1 ttl=46 time=1523 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=2 ttl=47 time=1494 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=3 ttl=47 time=1526 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=4 ttl=47 time=27.1 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=5 ttl=46 time=1499 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=6 ttl=46 time=1496 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=7 ttl=47 time=18.4 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=8 ttl=46 time=1496 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=9 ttl=47 time=27.8 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=10 ttl=46 time=986 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=11 ttl=46 time=496 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=12 ttl=47 time=18.4 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=13 ttl=46 time=1501 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=14 ttl=46 time=1016 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=15 ttl=47 time=28.0 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=16 ttl=47 time=17.8 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=17 ttl=47 time=1500 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=18 ttl=46 time=1526 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=19 ttl=46 time=1530 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=20 ttl=47 time=1497 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=21 ttl=47 time=18.4 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=22 ttl=46 time=990 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=23 ttl=47 time=24.3 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=24 ttl=47 time=1002 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=25 ttl=47 time=990 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=26 ttl=46 time=1520 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=27 ttl=47 time=1499 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=28 ttl=46 time=1495 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=29 ttl=46 time=1532 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=30 ttl=46 time=1016 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=31 ttl=47 time=17.9 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=32 ttl=46 time=1527 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=33 ttl=46 time=1019 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=34 ttl=47 time=988 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=35 ttl=46 time=1519 ms 64 bytes from ir2.fp.vip.bf1.yahoo.com (98.139.183.24): icmp_seq=36 ttl=46 time=1496 ms ^C --- yahoo.com ping statistics --- 37 packets transmitted, 36 received, 2% packet loss, time 48854ms rtt min/avg/max/mdev = 17.839/996.928/1532.515/613.551 ms
最佳答案
我对EC2微型实例的印象不一定是网络问题，而是CPU本身的循环。我猜对于微型实例，您正在从虚拟机上的其他实例接收剩余的CPU周期。因此，尽管随着时间的流逝，您将获得有保证的平均CPU周期数，但从短期来看，您已爆裂了它们，而不是拥有恒定的CPU能力。因此，我的猜测是，当您有CPU周期来响应ping时，可能已经为时已晚。因此，网络传输时间不是问题，但总体响应时间是问题。我在这里所说的只是我的猜测，可能无法反射(reflect)实际情况。
关于networking - EC2-微型实例-网络响应/延迟/延迟非常慢，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/9731864/