O'Reilly Velocity Web Performance and Operations http://velocityconf.com/ YSlow Best Practices for Speeding Up Your Web Site  | 1 Livid MOD PRO 确实不算快。测试结果来自洛杉矶。  |
 | 2 merryfreespace Jul 6, 2013 C:\>ping www.tukeji.com 正在 Ping www.tukeji.com [42.121.132.183] 具有 32 字节的数据: 请求超时。 来自 42.121.132.183 的回复: 字节=32 时间=358ms TTL=44 来自 42.121.132.183 的回复: 字节=32 时间=539ms TTL=44 来自 42.121.132.183 的回复: 字节=32 时间=352ms TTL=43 42.121.132.183 的 Ping 统计信息: 数据包: 已发送 = 4，已接收 = 3，丢失 = 1 (25% 丢失)， 往返行程的估计时间(以毫秒为单位): 最短 = 352ms，最长 = 539ms，平均 = 416ms C:\>ping tukeji-upload.b0.upaiyun.com 正在 Ping tukeji-upload.b0.upaiyun.com [119.145.147.56] 具有 32 字节的数据: 来自 119.145.147.56 的回复: 字节=32 时间=519ms TTL=44 来自 119.145.147.56 的回复: 字节=32 时间=360ms TTL=44 来自 119.145.147.56 的回复: 字节=32 时间=355ms TTL=44 来自 119.145.147.56 的回复: 字节=32 时间=361ms TTL=44 119.145.147.56 的 Ping 统计信息: 数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)， 往返行程的估计时间(以毫秒为单位): 最短 = 355ms，最长 = 519ms，平均 = 398ms C:\>ping f1g1ns1.dnspod.net 正在 Ping f1g1ns1.dnspod.net [119.167.195.12] 具有 32 字节的数据: 来自 119.167.195.12 的回复: 字节=32 时间=286ms TTL=46 来自 119.167.195.12 的回复: 字节=32 时间=280ms TTL=46 来自 119.167.195.12 的回复: 字节=32 时间=280ms TTL=46 来自 119.167.195.12 的回复: 字节=32 时间=294ms TTL=46 119.167.195.12 的 Ping 统计信息: 数据包: 已发送 = 4，已接收 = 4，丢失 = 0 (0% 丢失)， 往返行程的估计时间(以毫秒为单位): 最短 = 280ms，最长 = 294ms，平均 = 285ms |
 | 3 pala Jul 6, 2013 美东，宾州 ~ ping www.tukeji.com PING www.tukeji.com (42.121.132.183): 56 data bytes 64 bytes from 42.121.132.183: icmp_seq=0 ttl=41 time=331.294 ms 64 bytes from 42.121.132.183: icmp_seq=1 ttl=41 time=318.039 ms 64 bytes from 42.121.132.183: icmp_seq=2 ttl=41 time=341.690 ms ^C www.tukeji.com ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 318.039/330.341/341.690/9.679 ms ~ ping tukeji-upload.b0.upaiyun.com PING tukeji-upload.b0.upaiyun.com (122.225.29.168): 56 data bytes 64 bytes from 122.225.29.168: icmp_seq=0 ttl=44 time=461.922 ms 64 bytes from 122.225.29.168: icmp_seq=1 ttl=44 time=381.788 ms 64 bytes from 122.225.29.168: icmp_seq=2 ttl=45 time=405.449 ms 64 bytes from 122.225.29.168: icmp_seq=3 ttl=45 time=371.700 ms ^C --- tukeji-upload.b0.upaiyun.com ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 371.700/405.215/461.922/34.956 ms ~ ping f1g1ns1.dnspod.net PING f1g1ns1.dnspod.net (183.60.52.217): 56 data bytes 64 bytes from 183.60.52.217: icmp_seq=0 ttl=44 time=278.604 ms 64 bytes from 183.60.52.217: icmp_seq=1 ttl=44 time=281.590 ms 64 bytes from 183.60.52.217: icmp_seq=2 ttl=44 time=281.493 ms ^C --- f1g1ns1.dnspod.net ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 278.604/280.562/281.590/1.385 ms |
 | 5 Perry Jul 6, 2013 我的是不是来晚了。。Durham, NC  |
 | 7 TerranC OP 顺便问问有什么比较好的域名解析DNS推荐啊？免费的 |
 | 8 juicy Jul 6, 2013 |
 | 9 thinkxen /div> Jul 6, 2013 via Android 上一台香港的节点吧 |
| 11 TerranC OP @thinkxen 是说CDN还是？那如何解决写操作的丢包？其实网速不是太大问题，国外3G访问慢一点点也能接受，关键还是丢包，导致上传的东西总是失败。 |
 | 12 tzheng Jul 6, 2013 美中密苏里 noname-d8a25e937882:~ tian$ ping www.tukeji.com PING tukeji.com (42.121.132.183): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 ^C --- tukeji.com ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss noname-d8a25e937882:~ tian$ ping tukeji-upload.b0.upaiyun.com PING tukeji-upload.b0.upaiyun.com (112.90.179.66): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- tukeji-upload.b0.upaiyun.com ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss noname-d8a25e937882:~ tian$ ping f1g1ns1.dnspod.net PING f1g1ns1.dnspod.net (119.167.195.12): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- f1g1ns1.dnspod.net ping statistics --- 4 packets transmitted, 0 packets received, 100.0% packet loss |
| 14 tzheng Jul 6, 2013 @TerranC 我的错。。。我发现ping百度也不对。。应该是这会儿在的局域网封ping了 连了一个东北密苏里的vpn重ping: vh220006:~ tian$ ping www.tukeji.com PING tukeji.com (42.121.132.183): 56 data bytes 64 bytes from 42.121.132.183: icmp_seq=0 ttl=43 time=370.641 ms 64 bytes from 42.121.132.183: icmp_seq=1 ttl=43 time=303.126 ms 64 bytes from 42.121.132.183: icmp_seq=2 ttl=43 time=352.957 ms ^C --- tukeji.com ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 303.126/342.241/370.641/28.585 ms vh220006:~ tian$ ping tukeji-upload.b0.upaiyun.com PING tukeji-upload.b0.upaiyun.com (112.90.179.66): 56 data bytes 64 bytes from 112.90.179.66: icmp_seq=0 ttl=48 time=300.464 ms 64 bytes from 112.90.179.66: icmp_seq=1 ttl=48 time=447.943 ms 64 bytes from 112.90.179.66: icmp_seq=2 ttl=48 time=387.071 ms ^C --- tukeji-upload.b0.upaiyun.com ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 300.464/378.493/447.943/60.513 ms vh220006:~ tian$ ping f1g1ns1.dnspod.net PING f1g1ns1.dnspod.net (119.167.195.12): 56 data bytes Request timeout for icmp_seq 0 64 bytes from 119.167.195.12: icmp_seq=1 ttl=49 time=255.702 ms 64 bytes from 119.167.195.12: icmp_seq=2 ttl=49 time=253.360 ms 64 bytes from 119.167.195.12: icmp_seq=3 ttl=49 time=253.392 ms ^C --- f1g1ns1.dnspod.net ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 253.360/254.151/255.702/1.097 ms |
 | 15 pianai Jul 6, 2013  1 LasVegas root@pianai:~# ping www.tukeji.com PING tukeji.com (42.121.132.183) 56(84) bytes of data. 64 bytes from 42.121.132.183: icmp_req=1 ttl=46 time=210 ms 64 bytes from 42.121.132.183: icmp_req=2 ttl=46 time=294 ms 64 bytes from 42.121.132.183: icmp_req=3 ttl=46 time=207 ms 64 bytes from 42.121.132.183: icmp_req=4 ttl=46 time=203 ms 64 bytes from 42.121.132.183: icmp_req=5 ttl=46 time=201 ms 64 bytes from 42.121.132.183: icmp_req=6 ttl=46 time=207 ms ^C --- tukeji.com ping statistics --- 7 packets transmitted, 6 received, 14% packet loss, time 6000ms rtt min/avg/max/mdev = 201.901/220.731/294.131/32.946 ms root@pianai:~# ping tukeji-upload.b0.upaiyun.com PING tukeji-upload.b0.upaiyun.com (182.118.38.200) 56(84) bytes of data. 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=2 ttl=51 time=222 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=3 ttl=51 time=221 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=4 ttl=51 time=224 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=5 ttl=51 time=221 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=6 ttl=51 time=227 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=7 ttl=51 time=235 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=8 ttl=51 time=292 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=9 ttl=51 time=248 ms 64 bytes from hn.kd.ny.adsl (182.118.38.200): icmp_req=10 ttl=51 time=245 ms ^C --- tukeji-upload.b0.upaiyun.com ping statistics --- 10 packets transmitted, 9 received, 10% packet loss, time 8999ms rtt min/avg/max/mdev = 221.207/237.768/292.889/21.824 ms root@pianai:~# ping f1g1ns1.dnspod.net PING f1g1ns1.dnspod.net (183.60.52.217) 56(84) bytes of data. 64 bytes from 183.60.52.217: icmp_req=1 ttl=49 time=177 ms 64 bytes from 183.60.52.217: icmp_req=2 ttl=49 time=177 ms 64 bytes from 183.60.52.217: icmp_req=3 ttl=49 time=177 ms 64 bytes from 183.60.52.217: icmp_req=4 ttl=49 time=178 ms 64 bytes from 183.60.52.217: icmp_req=5 ttl=49 time=177 ms 64 bytes from 183.60.52.217: icmp_req=6 ttl=49 time=177 ms ^C --- f1g1ns1.dnspod.net ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5005ms rtt min/avg/max/mdev = 177.846/177.955/178.050/0.350 ms |
 | 16 lanbing Jul 6, 2013 服务器放香港或者韩国吧,阿里云出去太不给力. DNS用POWERDNS,稳定.国内外都能访问. 云存储可以考虑加上CDN. |
 | 18 zorceta Jul 6, 2013 1 |
 | 19 sharpnk Jul 6, 2013 PING tukeji.com (42.121.132.183): 56 data bytes 64 bytes from 42.121.132.183: icmp_seq=0 ttl=47 time=409.540 ms 64 bytes from 42.121.132.183: icmp_seq=1 ttl=47 time=408.507 ms 64 bytes from 42.121.132.183: icmp_seq=2 ttl=47 time=318.394 ms 64 bytes from 42.121.132.183: icmp_seq=3 ttl=47 time=319.713 ms 64 bytes from 42.121.132.183: icmp_seq=4 ttl=47 time=408.914 ms 64 bytes from 42.121.132.183: icmp_seq=5 ttl=47 time=318.423 ms 64 bytes from 42.121.132.183: icmp_seq=6 ttl=47 time=319.718 ms ^C --- tukeji.com ping statistics --- 8 packets transmitted, 7 packets received, 12.5% packet loss round-trip min/avg/max/stddev = 318.394/357.601/409.540/44.505 ms PING tukeji-upload.b0.upaiyun.com (122.136.32.9): 56 data bytes 64 bytes from 122.136.32.9: icmp_seq=0 ttl=48 time=329.204 ms 64 bytes from 122.136.32.9: icmp_seq=1 ttl=48 time=304.686 ms 64 bytes from 122.136.32.9: icmp_seq=2 ttl=48 time=323.011 ms 64 bytes from 122.136.32.9: icmp_seq=3 ttl=48 time=325.712 ms ^C --- tukeji-upload.b0.upaiyun.com ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 304.686/320.653/329.204/9.477 ms PING f1g1ns1.dnspod.net (119.167.195.12): 56 data bytes 64 bytes from 119.167.195.12: icmp_seq=0 ttl=50 time=280.134 ms 64 bytes from 119.167.195.12: icmp_seq=1 ttl=50 time=302.359 ms 64 bytes from 119.167.195.12: icmp_seq=2 ttl=50 time=283.827 ms 64 bytes from 119.167.195.12: icmp_seq=3 ttl=50 time=293.669 ms ^C --- f1g1ns1.dnspod.net ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 280.134/289.997/302.359/8.684 ms PING opt.xdwscache.glb0.lxdns.com (183.136.156.182): 56 data bytes 64 bytes from 183.136.156.182: icmp_seq=0 ttl=48 time=373.764 ms 64 bytes from 183.136.156.182: icmp_seq=1 ttl=48 time=374.498 ms 64 bytes from 183.136.156.182: icmp_seq=2 ttl=48 time=373.889 ms ^C --- opt.xdwscache.glb0.lxdns.com ping statistics --- 4 packets transmitted, 3 packets received, 25.0% packet loss round-trip min/avg/max/stddev = 373.764/374.050/374.498/0.321 ms PING ns67.domaincontrol.com (216.69.185.44): 56 data bytes 64 bytes from 216.69.185.44: icmp_seq=0 ttl=52 time=85.913 ms 64 bytes from 216.69.185.44: icmp_seq=1 ttl=52 time=86.515 ms 64 bytes from 216.69.185.44: icmp_seq=2 ttl=52 time=86.532 ms 64 bytes from 216.69.185.44: icmp_seq=3 ttl=52 time=85.159 ms ^C --- ns67.domaincontrol.com ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 85.159/86.030/86.532/0.561 ms opendns@Halifax, Canada |
 | 20 wzzyj8 Jul 6, 2013 猜测你需要 http://just-dnslookup.com/index.php?vh=www.tukeji.com&c=&s=dns+lookup%21 和 http://just-ping.com/index.php?vh=www.tukeji.com&c=&s=ping%21 package loss的确略高，DNS服务器目前看来问题不是很大，考虑CDN吧 |
 | 21 Showfom PRO 阿里云的出口带宽和普通的上海电信之类的都差不多 要是国外的访客多的话，别用天朝的云服或VPS或者服务器或者CDN等任意产品，因为整个中国电信和中国联通的出口带宽就那么屁大点。 |
 | 22 andyhu Jul 7, 2013 @pianai 连vpn的同学都不靠谱，在vpn线路上ping相当于加上了自己电脑到vpn服务器的时间，要不是自己在国外，也只能ssh连上再ping，否则结果不准确 |
| 23 andyhu Jul 7, 2013 建议楼主不要在v2上问了吧，可以去www.17ce.com测试下，有很多国外的节点 |
 | 28 donald Jul 9, 2013 美东，verizon fios C:\Windows\system32>ping www.tukeji.com Pinging tukeji.com [42.121.132.183] with 32 bytes of data: Reply from 42.121.132.183: bytes=32 time=286ms TTL=246 Reply from 42.121.132.183: bytes=32 time=280ms TTL=246 Reply from 42.121.132.183: bytes=32 time=282ms TTL=246 Reply from 42.121.132.183: bytes=32 time=282ms TTL=246 Ping statistics for 42.121.132.183: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 280ms, Maximum = 286ms, Average = 282ms C:\Windows\system32>ping tukeji-upload.b0.upaiyun.com Pinging tukeji-upload.b0.upaiyun.com [119.145.147.56] with 32 bytes of data: Reply from 119.145.147.56: bytes=32 time=589ms TTL=247 Reply from 119.145.147.56: bytes=32 time=565ms TTL=247 Reply from 119.145.147.56: bytes=32 time=571ms TTL=247 Reply from 119.145.147.56: bytes=32 time=588ms TTL=247 Ping statistics for 119.145.147.56: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 565ms, Maximum = 589ms, Average = 578ms C:\Windows\system32>ping f1g1ns1.dnspod.net Pinging f1g1ns1.dnspod.net [183.60.52.217] with 32 bytes of data: Reply from 183.60.52.217: bytes=32 time=566ms TTL=247 Reply from 183.60.52.217: bytes=32 time=573ms TTL=247 Reply from 183.60.52.217: bytes=32 time=590ms TTL=247 Reply from 183.60.52.217: bytes=32 time=544ms TTL=247 Ping statistics for 183.60.52.217: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 544ms, Maximum = 590ms, Average = 568ms C:\Windows\system32>ping up.qiniudn.com Pinging opt.xdwscache.glb0.lxdns.com [218.92.227.120] with 32 bytes of data: Reply from 218.92.227.120: bytes=32 time=419ms TTL=246 Reply from 218.92.227.120: bytes=32 time=415ms TTL=246 Reply from 218.92.227.120: bytes=32 time=414ms TTL=246 Request timed out. Ping statistics for 218.92.227.120: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 414ms, Maximum = 419ms, Average = 416ms C:\Windows\system32>ping ns67.domaincontrol.com Pinging ns67.domaincontrol.com [216.69.185.44] with 32 bytes of data: Reply from 216.69.185.44: bytes=32 time=196ms TTL=247 Reply from 216.69.185.44: bytes=32 time=196ms TTL=247 Reply from 216.69.185.44: bytes=32 time=194ms TTL=247 Reply from 216.69.185.44: bytes=32 time=196ms TTL=247 Ping statistics for 216.69.185.44: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 194ms, Maximum = 196ms, Average = 195ms |
Select Language