我的一个实例是有一些不寻常的问题。执行ping任何网站极其缓慢。力争让SSH连接也相当糟糕了。
下面是一个ping到雅虎。任何想法可能是什么造成的？
数据平yahoo.com（98.139.183.24），56（84）个字节。 64个字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 1 TTL = 46时间= 1523 毫秒从ir2.fp.vip.bf1.yahoo.com 64字节（98.139.183.24）：icmp_seq = 2 TTL = 47时间= 1494毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 3 TTL = 47时间= 1526毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 4 TTL = 47时间= 27.1 毫秒从ir2.fp.vip.bf1.yahoo.com 64字节（98.139.183.24）：icmp_seq = 5 TTL = 46时间= 1499毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 6 TTL = 46时间= 1496毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 7 TTL = 47时间= 18.4 毫秒从ir2.fp.vip.bf1.yahoo.com 64字节（98.139.183.24）：icmp_seq = 8 TTL = 46时间= 1496毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 9 TTL = 47时间= 27.8毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 10 TTL = 46时间= 986 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 11 TTL = 46时间= 496毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 12 TTL = 47时间= 18.4毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 13 TTL = 46时间= 1501 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 14 TTL = 46时间= 1016毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 15 TTL = 47时间= 28.0毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 16 TTL = 47时间= 17.8 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 17 TTL = 47时间= 1500毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 18 TTL = 46时间= 1526毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 19 TTL = 46时间= 1530 毫秒从ir2.fp.vip.bf1.yahoo.com 64字节（98.139.183.24）：icmp_seq = 20 TTL = 47时间= 1497毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 21 TTL = 47时间= 18.4毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 22 TTL = 46时间= 990 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 23 TTL = 47时间= 24.3毫秒的64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 24 TTL = 47时间= 1002毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 25 TTL = 47时间= 990 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 26 TTL = 46时间= 1520毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 27 TTL = 47时间= 1499毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 28 TTL = 46时间= 1495 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 29 TTL = 46时间= 1532毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 30 TTL = 46时间= 1016毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 31 TTL = 47时间= 17.9 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 32 TTL = 46时间= 1527毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 33 TTL = 46时间= 1019毫秒64从字节 ir2.fp.vip.bf1.yahoo.com（98.139.183.24）：icmp_seq = 34 TTL = 47时间= 988 硕士学位ir2.fp.vip.bf1.yahoo.com 64个字节（98.139.183.24）：icmp_seq = 35 TTL = 46时间= 1519毫秒64个字节ir2.fp.vip.bf1.yahoo.com （98.139.183.24）：icmp_seq = 36 TTL = 46时间= 1496毫秒^ C --- yahoo.com ping统计--- 37包转发，36收到，2％的丢包率，时间48854ms RTT最小/平均/最大/ MDEV = 17.839 / 996.928 / 1532.515 / 613.551毫秒
解决方案我的IM pression与EC2实例微不一定是网络的问题，但CPU周期本身。我想用微实例，您收到遗留的其他情况下的CPU周期的虚拟机上。所以，尽管随着时间的推移，您将收到的CPU周期有保证的平均数，在短期内，你已经爆出他们有恒定的CPU功率来代替。所以，我的猜测是，当你的CPU周期来响应ping命令，这可能是为时已晚。因此，网络旅行时间不是问题，但总的响应时间。不管我说这是我的猜测，可能不能反映什么是真正回事。
One of my instances is having some unusual issues. Pinging any site is extremely slow. Trying to keep the SSH connection is quite crappy too.
The following is a ping to yahoo. Any idea what could be causing this?
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
解决方案
My impression with EC2 micro instance is not necessarily networking is the problem but CPU cycles itself. I guess with micro instance, you are receiving left-over CPU cycles from other instances on a virtual machine. So, although over time, you receive a guaranteed average number of CPU cycles, in short run, you have burst of them instead of having constant CPU power. So, my guess is that when you have CPU cycles to respond a ping, it might be already too late. So, network travel time is not the issue but overall respond time is. Whatever I say here is my guess and may not reflect what is really going on.
相关推荐
最新文章