EC2 - 微实例 - 网络响应/延迟/延迟非常慢

MKN*_*ons 9 networking amazon-ec2

我的一个例子是有一些不寻常的问题.Ping任何网站都非常慢.试图保持SSH连接也很糟糕.

以下是对雅虎的ping.知道是什么原因引起的吗?

PING yahoo.com(98.139.183.24)56(84)字节的数据.来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 1 ttl = 46 time = 1523 ms来自ir2.fp.vip.bf1.yahoo.com(98.139.183.24)的64字节: icmp_seq = 2 ttl = 47 time = 1494 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 3 ttl = 47 time = 1526 ms来自ir2.fp.vip.bf1的64字节.yahoo.com(98.139.183.24):icmp_seq = 4 ttl = 47 time = 27.1 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 5 ttl = 46 time = 1499 ms来自ir2.fp.vip.bf1.yahoo.com(98.139.183.24)的64字节:icmp_seq = 6 ttl = 46 time = 1496 ms来自ir2.fp.vip.bf1.yahoo.com(98.139.183.24)的64字节: icmp_seq = 7 ttl = 47 time = 18.4 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 8 ttl = 46 time = 1496 ms来自ir2.fp.vip.bf1的64字节.yahoo.com(98.139.183.24):icmp_seq = 9 ttl = 47 time = 27.8 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 10 ttl = 46 time = 986 ms来自ir2.fp.vip.bf1.yahoo.com(98.139.183.24)的64字节:icmp_seq = 11 ttl = 46 time = 496 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 12 ttl = 47 time = 18.4 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 13 ttl = 46 time = 1501 ms来自ir2的64字节. fp.vip.bf1.yahoo.com(98.139.183.24):icmp_seq = 14 ttl = 46 time = 1016 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 15 ttl = 47次= 28.0 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 16 ttl = 47 time = 17.8 ms来自ir2.fp.vip.bf1.yahoo.com的64字节( 98.139.183.24):icmp_seq = 17 ttl = 47 time = 1500 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 18 ttl = 46 time = 1526 ms来自ir2的64字节. fp.vip.bf1.yahoo.com(98.139.183.24):icmp_seq = 19 ttl = 46 time = 1530 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 20 ttl = 47次= 1497 ms 64字节来自ir2.fp.vip.bf1.yahoo.com(98.139.183.24):icmp_seq = 21 ttl = 47 time = 18.4 ms 64字节来自ir2.fp.vip.bf1.yahoo.com( 98.139.183.24):icmp_seq = 22 ttl = 46 time = 990 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 23 ttl = 47 t ime = 24.3 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 24 ttl = 47 time = 1002 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139) .183.24):icmp_seq = 25 ttl = 47 time = 990 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 26 ttl = 46 time = 1520 ms来自ir2.fp的64字节.vip.bf1.yahoo.com(98.139.183.24):icmp_seq = 27 ttl = 47 time = 1499 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 28 ttl = 46时间= 1495 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 29 ttl = 46 time = 1532 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139) .183.24):icmp_seq = 30 ttl = 46 time = 1016 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 31 ttl = 47 time = 17.9 ms来自ir2.fp的64字节.vip.bf1.yahoo.com(98.139.183.24):icmp_seq = 32 ttl = 46 time = 1527 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 33 ttl = 46时间= 1019 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 34 ttl = 47 time = 988 ms来自ir2.fp.v的64字节 ip.bf1.yahoo.com(98.139.183.24):icmp_seq = 35 ttl = 46 time = 1519 ms来自ir2.fp.vip.bf1.yahoo.com的64字节(98.139.183.24):icmp_seq = 36 ttl = 46 time = 1496 ms ^ C --- yahoo.com ping统计数据---发送37个数据包,收到36个数据包,丢失2%,时间48854m​​s rtt min/avg/max/mdev = 17.839/996.928/1532.515/613.551 ms

tar*_*tar 15

我对EC2微实例的印象不一定是网络问题,但CPU循环本身.我想在micro实例中,您正在从虚拟机上的其他实例接收剩余的CPU周期.因此,虽然随着时间的推移,您可以获得保证的平均CPU周期数,但在短期内,您可以使用它们而不是拥有恒定的CPU功率.所以,我的猜测是,当你有CPU周期来响应ping时,可能已经太晚了.因此,网络旅行时间不是问题,但总体响应时间是.无论我在这里说什么都是我的猜测,可能无法反映真实情况.

  • 所以答案是正确的,这是CPU周期. (3认同)