最新消息:VPS服务器又从fzhost.net换回Linode了,主题仍用朋友推荐的大前端D8

【考虑】crifan.com的VPS换vultr or Linode更换服务器机房

crifan.com crifan 206浏览 0评论

最近的Linode的Atlanta的VPS,国内江苏电信连接的速度又慢死了:

https://www.linode.com/speedtest

-》

【2017-11-16 晚上】

http://speedtest.atlanta.linode.com/100MB-atlanta.bin

【2017-11-17 早上 09:00】

看了:

Sugarhosts主机的速度怎么样? | Sugarhosts主机评论

【糖果主机Sugarhosts】5大机房速评测及国内购买机房推荐-蜗牛789

-》国内访问速度貌似真的很好?

SugarHosts洛杉矶MC机房VPS主机配置、速度及UnixBench跑分综合评测 | 老左博客

但是:“每次看到SugarHosts评测, 基本都是好评居多, 今天终于下定决心购入一台vps, 用电信, 移动, 华数测试速度, 移动稍好, 但其它掉包率在10%以上, 马上申请退, 结果是不支持任何理由退, 就是不退, 很有国人风范, 给大家提个醒了

2015-08-01 下午 10:24 [回复]

  • jessy:

    刚买他们家的主机,网速不稳定,延迟大,服务态度差,建议不要购买。比他家好的到处都是

    2015-08-09 下午 5:28 [回复]

    • 老左:

      你买的哪个机房的?洛杉矶MC的最近普遍有点不稳定,直连的还可以。”

Linux SSD VPS Hosting | XEN Technology | High Performance Hosting – SugarHosts

官网SSD的VPS只有:

sugarhosts VPS 网速 vs Linode VPS

四大 VPS 对比评测:Linode vs. DigitalOcean vs. Lightsail vs. Vultr – 小众软件

【总结】

总体感觉,貌似是:

1.优先换

High Performance and Cheap Cloud Servers Deployment – Vultr.com

价格:和Linode基本上一样

速度:不清楚,估计比现在好吧

【后记 171121】

又给了自己的crifan.com的Linode的Atalanta测试了:

linode的speedtest下载速度:80KB左右,一般般

去其他测试网址给https://www.crifan.com测速:

http://www.17ce.com/site/http/201710_6436a91b835780148b24b8f644c6de70.html

结果也还是很不好:

-》所以还是要抽空去换服务器才行。

vultr 网速

Vultr 的东京和洛杉矶机房,哪个更好? – 知乎

-》抽空用mtr测速VPS连接速度

vultr各节点测试地址[官方] – Vultr VPS

-》可以去下载测试 -〉 只能供参考,和实际网站放上去的速度不一定一致。

Largest Cloud Server Network Available – Vultr.com

-》Vultr.com Frequently Asked Questions – Vultr.com

2018-0122 10:30左右:

➜  youtubeSubtitle ping fra-de-ping.vultr.com

PING fra-de-ping.vultr.com (108.61.210.117): 56 data bytes

64 bytes from 108.61.210.117: icmp_seq=0 ttl=48 time=319.607 ms

64 bytes from 108.61.210.117: icmp_seq=1 ttl=48 time=339.976 ms

64 bytes from 108.61.210.117: icmp_seq=2 ttl=48 time=259.846 ms

64 bytes from 108.61.210.117: icmp_seq=3 ttl=48 time=255.774 ms

64 bytes from 108.61.210.117: icmp_seq=4 ttl=48 time=300.855 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- fra-de-ping.vultr.com ping statistics —

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 255.774/295.212/339.976/32.975 ms

➜  youtubeSubtitle ping par-fr-ping.vultr.com

PING par-fr-ping.vultr.com (108.61.209.127): 56 data bytes

64 bytes from 108.61.209.127: icmp_seq=0 ttl=49 time=318.180 ms

Request timeout for icmp_seq 1

64 bytes from 108.61.209.127: icmp_seq=2 ttl=49 time=260.467 ms

64 bytes from 108.61.209.127: icmp_seq=3 ttl=49 time=279.899 ms

64 bytes from 108.61.209.127: icmp_seq=4 ttl=49 time=209.558 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- par-fr-ping.vultr.com ping statistics —

5 packets transmitted, 4 packets received, 20.0% packet loss

round-trip min/avg/max/stddev = 209.558/267.026/318.180/39.141 ms

➜  youtubeSubtitle ping ams-nl-ping.vultr.com

PING ams-nl-ping.vultr.com (108.61.198.102): 56 data bytes

64 bytes from 108.61.198.102: icmp_seq=0 ttl=49 time=189.369 ms

64 bytes from 108.61.198.102: icmp_seq=1 ttl=49 time=193.938 ms

64 bytes from 108.61.198.102: icmp_seq=2 ttl=49 time=202.268 ms

64 bytes from 108.61.198.102: icmp_seq=3 ttl=49 time=195.538 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- ams-nl-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 189.369/195.278/202.268/4.627 ms

➜  youtubeSubtitle ping lon-gb-ping.vultr.com

PING lon-gb-ping.vultr.com (108.61.196.101): 56 data bytes

64 bytes from 108.61.196.101: icmp_seq=0 ttl=49 time=426.618 ms

64 bytes from 108.61.196.101: icmp_seq=1 ttl=49 time=513.646 ms

Request timeout for icmp_seq 2

64 bytes from 108.61.196.101: icmp_seq=3 ttl=49 time=793.040 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- lon-gb-ping.vultr.com ping statistics —

5 packets transmitted, 3 packets received, 40.0% packet loss

round-trip min/avg/max/stddev = 426.618/577.768/793.040/156.312 ms

➜  youtubeSubtitle ping sgp-ping.vultr.com

PING sgp-ping.vultr.com (45.32.100.168): 56 data bytes

64 bytes from 45.32.100.168: icmp_seq=0 ttl=48 time=158.214 ms

64 bytes from 45.32.100.168: icmp_seq=1 ttl=48 time=158.654 ms

64 bytes from 45.32.100.168: icmp_seq=2 ttl=48 time=159.691 ms

64 bytes from 45.32.100.168: icmp_seq=3 ttl=48 time=158.299 ms

64 bytes from 45.32.100.168: icmp_seq=4 ttl=48 time=159.580 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- sgp-ping.vultr.com ping statistics —

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 158.214/158.888/159.691/0.629 ms

➜  youtubeSubtitle ping nj-us-ping.vultr.com

PING nj-us-ping.vultr.com (108.61.149.182): 56 data bytes

64 bytes from 108.61.149.182: icmp_seq=0 ttl=47 time=210.758 ms

64 bytes from 108.61.149.182: icmp_seq=1 ttl=47 time=274.577 ms

64 bytes from 108.61.149.182: icmp_seq=2 ttl=47 time=209.793 ms

64 bytes from 108.61.149.182: icmp_seq=3 ttl=47 time=313.466 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- nj-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 209.793/252.149/313.466/44.074 ms

➜  youtubeSubtitle ping hnd-jp-ping.vultr.com

PING hnd-jp-ping.vultr.com (108.61.201.151): 56 data bytes

64 bytes from 108.61.201.151: icmp_seq=0 ttl=50 time=116.553 ms

64 bytes from 108.61.201.151: icmp_seq=1 ttl=50 time=117.448 ms

64 bytes from 108.61.201.151: icmp_seq=2 ttl=50 time=117.399 ms

64 bytes from 108.61.201.151: icmp_seq=3 ttl=50 time=118.097 ms

64 bytes from 108.61.201.151: icmp_seq=4 ttl=50 time=117.805 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- hnd-jp-ping.vultr.com ping statistics —

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 116.553/117.460/118.097/0.520 ms

➜  youtubeSubtitle ping il-us-ping.vultr.com

PING il-us-ping.vultr.com (107.191.51.12): 56 data bytes

64 bytes from 107.191.51.12: icmp_seq=0 ttl=49 time=364.140 ms

64 bytes from 107.191.51.12: icmp_seq=1 ttl=49 time=369.930 ms

64 bytes from 107.191.51.12: icmp_seq=2 ttl=49 time=372.088 ms

64 bytes from 107.191.51.12: icmp_seq=3 ttl=49 time=420.480 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- il-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 364.140/381.659/420.480/22.601 ms

➜  youtubeSubtitle ping ga-us-ping.vultr.com

PING ga-us-ping.vultr.com (108.61.193.166): 56 data bytes

64 bytes from 108.61.193.166: icmp_seq=0 ttl=49 time=364.376 ms

64 bytes from 108.61.193.166: icmp_seq=1 ttl=49 time=351.274 ms

64 bytes from 108.61.193.166: icmp_seq=2 ttl=49 time=372.788 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- ga-us-ping.vultr.com ping statistics —

3 packets transmitted, 3 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 351.274/362.813/372.788/8.852 ms

➜  youtubeSubtitle ping fl-us-ping.vultr.com

PING fl-us-ping.vultr.com (104.156.244.232): 56 data bytes

64 bytes from 104.156.244.232: icmp_seq=0 ttl=49 time=483.183 ms

64 bytes from 104.156.244.232: icmp_seq=1 ttl=49 time=400.271 ms

64 bytes from 104.156.244.232: icmp_seq=2 ttl=49 time=420.361 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- fl-us-ping.vultr.com ping statistics —

4 packets transmitted, 3 packets received, 25.0% packet loss

round-trip min/avg/max/stddev = 400.271/434.605/483.183/35.315 ms

➜  youtubeSubtitle ping wa-us-ping.vultr.com

PING wa-us-ping.vultr.com (108.61.194.105): 56 data bytes

64 bytes from 108.61.194.105: icmp_seq=0 ttl=46 time=392.265 ms

64 bytes from 108.61.194.105: icmp_seq=1 ttl=46 time=313.280 ms

64 bytes from 108.61.194.105: icmp_seq=2 ttl=46 time=329.487 ms

64 bytes from 108.61.194.105: icmp_seq=3 ttl=46 time=346.255 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- wa-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 313.280/345.322/392.265/29.504 ms

➜  youtubeSubtitle ping tx-us-ping.vultr.com

PING tx-us-ping.vultr.com (108.61.224.175): 56 data bytes

64 bytes from 108.61.224.175: icmp_seq=0 ttl=49 time=203.737 ms

64 bytes from 108.61.224.175: icmp_seq=1 ttl=49 time=202.954 ms

64 bytes from 108.61.224.175: icmp_seq=2 ttl=49 time=202.671 ms

64 bytes from 108.61.224.175: icmp_seq=3 ttl=49 time=202.215 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- tx-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 202.215/202.894/203.737/0.553 ms

➜  youtubeSubtitle ping sjo-ca-us-ping.vultr.com

PING sjo-ca-us-ping.vultr.com (104.156.230.107): 56 data bytes

64 bytes from 104.156.230.107: icmp_seq=0 ttl=49 time=299.212 ms

64 bytes from 104.156.230.107: icmp_seq=1 ttl=49 time=268.370 ms

64 bytes from 104.156.230.107: icmp_seq=2 ttl=49 time=250.708 ms

64 bytes from 104.156.230.107: icmp_seq=3 ttl=49 time=247.207 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- sjo-ca-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 247.207/266.374/299.212/20.586 ms

➜  youtubeSubtitle ping lax-ca-us-ping.vultr.com

PING lax-ca-us-ping.vultr.com (108.61.219.200): 56 data bytes

64 bytes from 108.61.219.200: icmp_seq=0 ttl=50 time=253.929 ms

64 bytes from 108.61.219.200: icmp_seq=1 ttl=50 time=235.200 ms

64 bytes from 108.61.219.200: icmp_seq=2 ttl=50 time=257.650 ms

64 bytes from 108.61.219.200: icmp_seq=3 ttl=50 time=210.054 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- lax-ca-us-ping.vultr.com ping statistics —

4 packets transmitted, 4 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 210.054/239.208/257.650/18.860 ms

➜  youtubeSubtitle ping syd-au-ping.vultr.com

PING syd-au-ping.vultr.com (108.61.212.117): 56 data bytes

64 bytes from 108.61.212.117: icmp_seq=0 ttl=46 time=244.187 ms

64 bytes from 108.61.212.117: icmp_seq=1 ttl=46 time=326.743 ms

64 bytes from 108.61.212.117: icmp_seq=2 ttl=46 time=229.055 ms

64 bytes from 108.61.212.117: icmp_seq=3 ttl=46 time=306.740 ms

64 bytes from 108.61.212.117: icmp_seq=4 ttl=46 time=230.254 ms

^C

<span style="font-size: 12px; color: rgb(51, 51, 51); font-family: Monaco;"–<- syd-au-ping.vultr.com ping statistics —

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 229.055/267.396/326.743/41.130 ms

-》看来还是日本和新加坡的速度比较不错,大概不到200ms

其他都还是有点慢

-〉如果都能稳定在200多ms,其实我也能接受

-》就怕像现在江苏电信访问Linode的LA的VPS,有时候好有时候坏,那就郁闷了。

Vultr 的东京和洛杉矶机房,哪个更好? – 知乎

“谷歌的TCP-BBR技术”

-》抽空去试试BBR

Vultr 大家的下载速度都是多少? – V2EX

锐速?

Vultr各个节点速度测试-详细内容-黄兵的个人博客

Vultr各地区机房下载速度测试 Vultr VPS测速地址 – NMB HOST

【总结】

抽空用:

  • MTR去测试连接速度

  • 继续去看看:

  • 抽空查查Google的TCP-BBR是啥,看看所说的加速技术看看效果

  • 抽空也查查锐速是啥,如何加速

2018-01-22 15:10

此刻的速度是:

-》所以至少此刻vultr的(新加坡和日本)速度是比Linode(的atlanta)的速度要快很多的。

2018年最好的国外VPS推荐 —— 购买指南 – 十佳评测

https://www.linode.com/speedtest

2018-03-15 11:00

苏州移动

2018-03-15 11:00测试结果:

  • newark: 4.4MB/s

  • fremont: 3MB/s

  • singapore: 1.2MB/s

  • tokyo2: 800KB/s

  • london: 300KB/s

ping的结果:

<code>
➜  youtubeSubtitle git:(master) ✗ ping speedtest.newark.linode.com
PING speedtest.newark.linode.com (50.116.57.237): 56 data bytes
64 bytes from 50.116.57.237: icmp_seq=0 ttl=52 time=253.327 ms
64 bytes from 50.116.57.237: icmp_seq=1 ttl=52 time=259.575 ms
64 bytes from 50.116.57.237: icmp_seq=2 ttl=52 time=280.240 ms
^C
--- speedtest.newark.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 253.327/264.381/280.240/11.501 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.atlanta.linode.com
PING speedtest.atlanta.linode.com (50.116.39.117): 56 data bytes
64 bytes from 50.116.39.117: icmp_seq=0 ttl=48 time=298.218 ms
64 bytes from 50.116.39.117: icmp_seq=1 ttl=48 time=321.345 ms
64 bytes from 50.116.39.117: icmp_seq=2 ttl=48 time=342.718 ms
^C
--- speedtest.atlanta.linode.com ping statistics ---
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 298.218/320.760/342.718/18.172 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.dallas.linode.com
PING speedtest.dallas.linode.com (50.116.25.154): 56 data bytes
64 bytes from 50.116.25.154: icmp_seq=0 ttl=43 time=324.769 ms
64 bytes from 50.116.25.154: icmp_seq=1 ttl=43 time=343.650 ms
64 bytes from 50.116.25.154: icmp_seq=2 ttl=43 time=264.958 ms
^C
--- speedtest.dallas.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 264.958/311.126/343.650/33.543 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.fremont.linode.com
PING speedtest.fremont.linode.com (50.116.14.9): 56 data bytes
64 bytes from 50.116.14.9: icmp_seq=0 ttl=52 time=200.310 ms
64 bytes from 50.116.14.9: icmp_seq=1 ttl=52 time=199.732 ms
64 bytes from 50.116.14.9: icmp_seq=2 ttl=52 time=199.061 ms
^C
--- speedtest.fremont.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 199.061/199.701/200.310/0.510 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.frankfurt.linode.com
PING speedtest.frankfurt.linode.com (139.162.130.8): 56 data bytes
64 bytes from 139.162.130.8: icmp_seq=0 ttl=53 time=193.970 ms
64 bytes from 139.162.130.8: icmp_seq=1 ttl=53 time=192.356 ms
64 bytes from 139.162.130.8: icmp_seq=2 ttl=53 time=194.414 ms
^C
--- speedtest.frankfurt.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 192.356/193.580/194.414/0.884 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.london.linode.com
PING speedtest.london.linode.com (176.58.107.39): 56 data bytes
64 bytes from 176.58.107.39: icmp_seq=0 ttl=53 time=332.032 ms
64 bytes from 176.58.107.39: icmp_seq=1 ttl=53 time=248.407 ms
64 bytes from 176.58.107.39: icmp_seq=2 ttl=53 time=231.295 ms
^C
--- speedtest.london.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 231.295/270.578/332.032/44.013 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.singapore.linode.com
PING speedtest.singapore.linode.com (139.162.23.4): 56 data bytes
64 bytes from 139.162.23.4: icmp_seq=0 ttl=45 time=94.941 ms
64 bytes from 139.162.23.4: icmp_seq=1 ttl=45 time=91.618 ms
64 bytes from 139.162.23.4: icmp_seq=2 ttl=45 time=94.708 ms
^C
--- speedtest.singapore.linode.com ping statistics ---
4 packets transmitted, 3 packets received, 25.0% packet loss
round-trip min/avg/max/stddev = 91.618/93.756/94.941/1.515 ms
➜  youtubeSubtitle git:(master) ✗ ping speedtest.tokyo2.linode.com
PING speedtest.shg1.linode.com (139.162.65.37): 56 data bytes
64 bytes from 139.162.65.37: icmp_seq=0 ttl=45 time=106.285 ms
64 bytes from 139.162.65.37: icmp_seq=1 ttl=45 time=114.874 ms
64 bytes from 139.162.65.37: icmp_seq=2 ttl=45 time=111.919 ms
^C
--- speedtest.shg1.linode.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 106.285/111.026/114.874/3.563 ms
</code>

还是tokyo2和singapore速度最快

目前可选服务器:

-》如果现在速度慢,而发现其他某个服务器速度快,则去提交工单,申请换位置

抽空继续测测Linode的不同服务器的效果

【已解决】Linode的VPS中的Tokyo2节点机房服务器速度如何

【已解决】Mac中测试目标IP的路由线路图

所以还是抽空换到tokyo2去吧。

继续测速:

2018-03-16 14:00

苏州移动

最后只有:atlanta和singapore速度最慢

其他都还不错:

  • newark

  • dallas

  • frankfurt

  • fremont

  • tokyo2

  • london

2018-03-16 23:00

苏州电信

竟然newark速度很慢,而且tokyo2也很慢

只有Fremont速度不错

<code>➜  ~ ping speedtest.tokyo2.linode.com
PING speedtest.shg1.linode.com (139.162.65.37): 56 data bytes
64 bytes from 139.162.65.37: icmp_seq=0 ttl=50 time=220.902 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 139.162.65.37: icmp_seq=5 ttl=50 time=220.182 ms
^C
--- speedtest.shg1.linode.com ping statistics ---
6 packets transmitted, 2 packets received, 66.7% packet loss
round-trip min/avg/max/stddev = 220.182/220.542/220.902/0.360 ms
➜  ~ ping speedtest.atlanta.linode.com
PING speedtest.atlanta.linode.com (50.116.39.117): 56 data bytes
64 bytes from 50.116.39.117: icmp_seq=0 ttl=45 time=382.851 ms
64 bytes from 50.116.39.117: icmp_seq=1 ttl=45 time=383.390 ms
64 bytes from 50.116.39.117: icmp_seq=2 ttl=45 time=381.861 ms
64 bytes from 50.116.39.117: icmp_seq=3 ttl=45 time=381.974 ms
64 bytes from 50.116.39.117: icmp_seq=4 ttl=45 time=381.425 ms
^C
--- speedtest.atlanta.linode.com ping statistics ---
6 packets transmitted, 5 packets received, 16.7% packet loss
round-trip min/avg/max/stddev = 381.425/382.300/383.390/0.715 ms
</code>

2018-03-16 09:30

苏州电信 100M

截至目前:

london:不论电信还是移动,速度都还凑合。高的有2MB,少的也有100多KB,所以也还可以了。

2018-03-18 14:00

苏州电信

london:2.7MB

fremont:2.7MB

frankfurt:300多KB

其他包括atlanta,tokyo2等,速度都是10KB级别的,很慢

-》

还是london速度比较稳定。

2018-03-18 21:00

苏州电信

dallas:3.3MB

london:770KB

newark:200KB

fremont:160KB

frankfurt:120KB

tokyo2:50KB

atlanta,singapore,都是慢到没有速度的

所以,目前结论是:

还是london的速度相对来说,

对于苏州电信和苏州移动,

以及对于不同时间段,

速度都还是能接受的:

最低也有100KB以上

最高有2,3MB

所以算能接受的。

(而其他节点,无法同时满足,移动和电信速度都很好)

【后记】

在把服务器从atlanta更换到london后,再去测速

苏州电信

此刻:

london:700KB

而atlanta:4KB

真的是需要更换。

但是:

此处去ping,速度很不稳定:

<code>➜  naturling_homepage git:(master) ping www.crifan.com
PING www.crifan.com (80.85.87.205): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 80.85.87.205: icmp_seq=1 ttl=50 time=467.688 ms
Request timeout for icmp_seq 2
64 bytes from 80.85.87.205: icmp_seq=3 ttl=50 time=514.606 ms
Request timeout for icmp_seq 4
64 bytes from 80.85.87.205: icmp_seq=5 ttl=50 time=423.856 ms
64 bytes from 80.85.87.205: icmp_seq=6 ttl=50 time=473.253 ms
^C
--- www.crifan.com ping statistics ---
8 packets transmitted, 4 packets received, 50.0% packet loss
round-trip min/avg/max/stddev = 423.856/469.851/514.606/32.151 ms
➜  naturling_homepage git:(master) ping www.crifan.com
PING www.crifan.com (80.85.87.205): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 80.85.87.205: icmp_seq=1 ttl=50 time=446.347 ms
64 bytes from 80.85.87.205: icmp_seq=2 ttl=50 time=468.326 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
64 bytes from 80.85.87.205: icmp_seq=7 ttl=50 time=474.171 ms
64 bytes from 80.85.87.205: icmp_seq=8 ttl=50 time=497.147 ms
64 bytes from 80.85.87.205: icmp_seq=9 ttl=50 time=518.721 ms
^C
--- www.crifan.com ping statistics ---
11 packets transmitted, 5 packets received, 54.5% packet loss
round-trip min/avg/max/stddev = 446.347/480.942/518.721/24.866 ms
</code>

而浏览器访问crifan.com也还是很慢。

哎,只能说凑合用把。还是不是很完美。

转载请注明:在路上 » 【考虑】crifan.com的VPS换vultr or Linode更换服务器机房

发表我的评论
取消评论

表情

Hi,您需要填写昵称和邮箱!

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址
15 queries in 0.247 seconds, using 10.38MB memory