Vultr 澳大利亚(墨尔本)VPS测评,适合大洋洲的业务,硬盘i/O良好,线路绕道,延迟较高

今年 Vultr 拓展机房的速度属于火力全开,不断开放新的数据中心,从年初到现在,共发布了3个数据中心,在以往一年能发布一个数据中心,就算谢天谢地了,这次真是大气了。借着这个机会,站长购入了一台澳大利亚(墨尔本)VPS,对这个地区的VPS进行数据测评,看看澳大利亚墨尔本VPS适不适合国内小伙伴,并且看看具体性能怎么样、路由的走向、延迟、媒体解锁以及UnixBench跑分情况,下面站长就一一进行测评。

202012111703271607677407

官网:https://www.vultr.com/

测评所用VPS配置信息
  • CPU:1核
  • 内存:1G
  • 硬盘:25G SSD
  • 流量:1000G
  • 带宽:1Gbps
  • 机房:澳大利亚墨尔本
  • 价格:$5/月
赠金100美元 购买链接

一、基本信息

CPU内核可以达到 2992 MHz,硬盘 I/O 平均可以跑到1.6GB/s,非常优秀了,商家没有对I/O进行限制

iShot2022 02 13 22.11.08

二、性能测试

CPU、内存、硬盘跑分大家可以随便看看

iShot2022 02 13 22.13.45

三、机房测速

iShot2022 02 13 22.11.28
iShot2022 02 13 22.02.11

四、PING延迟

区域最快/最慢平均
全网澳大利亚墨尔本(ZENLAYER-MEL1) 0.3ms/江苏南通(移动) 832.5ms259.6ms
移动上海(移动云) 291.2ms/江苏南通(移动) 832.5ms372.2ms
联通安徽合肥(联通-菠萝云) 284.7ms/吉林延边(联通) 336.6ms311.8ms
电信河北保定(天翼云) 294.0ms/福建福州(移动-云端) 362.2ms318.8ms
华南广东深圳(阿里云) 273.4ms / 广东深圳(移动-速云) 420.2ms309.7ms
华北北京(百度云) 290.0ms / 内蒙古呼和浩特(移动云) 367.3ms317.6ms
华东上海地面通(CN2) 159.8ms / 江苏南通(移动) 832.5ms325.9ms
华中河南洛阳(bgp) 299.1ms / 河南郑州(移动云) 376.2ms327.7ms
东北辽宁沈阳(天翼云三区) 314.9ms / 辽宁沈阳LM2(移动) 388.2ms336.3ms
西北陕西西安(天翼云二区) 301.2ms / 新疆乌鲁木齐(天翼云) 333.9ms317.0ms
西南重庆(移动云) 309.1ms / 四川成都(移动) 395.5ms331.2ms
港澳台香港(Azure) 122.5ms / 香港(CN2-90idc.net) 291.7ms171.9ms
亚洲新加坡(Azure) 92.5ms/哈萨克斯坦阿拉木图 493.1ms180.6ms
欧洲俄罗斯伯力(misaka.io) 176.7ms/土耳其伊斯坦布尔(ZENLAYER-IST1) 446.4ms274.9ms
非洲肯尼亚内罗毕 269.7ms/南非约翰内斯堡(oneprovider) 436.9ms357.0ms
北美洲美国圣克拉拉(Azure) 148.5ms/哥斯达黎加圣何塞 322.3ms239.0ms
南美洲智利圣地亚哥(GCP) 253.5ms/智利比尼亚德尔马 450.9ms378.8ms
大洋洲澳大利亚墨尔本(ZENLAYER-MEL1) 0.3ms/澳大利亚悉尼(AMAZON-LIGHTSAIL) 238.8ms29.0ms
iShot2022 02 14 01.34.34

五、媒体流解锁

iShot2022 02 14 23.56.46

六、去程路由

江苏电信去程
iShot2022 02 14 01.30.17
江苏联通去程
iShot2022 02 14 01.33.04
江苏移动去程
iShot2022 02 14 01.32.05

七、回程路由

北京、上海、广州电信回程
Traceroute to China, Beijing CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.149.128.1 (180.149.128.1), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  *
 6  141.136.110.41  240.52 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 7  141.136.110.41  241.09 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 8  154.14.32.238  261.42 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 9  202.97.12.49  276.67 ms  AS4134  China, Beijing, ChinaTelecom
10  202.97.81.141  276.98 ms  AS4134  China, Beijing, ChinaTelecom
11  *
12  180.149.128.1  311.66 ms  AS23724  China, Beijing, ChinaTelecom
Traceroute to China, Shanghai CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.153.28.1 (180.153.28.1), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  *
 6  141.136.110.41  245.44 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 7  141.136.110.41  241.08 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 8  *
 9  202.97.50.194  286.26 ms  AS4134  China, Shanghai, ChinaTelecom
10  202.97.50.194  287.90 ms  AS4134  China, Shanghai, ChinaTelecom
11  202.97.57.18  301.64 ms  AS4134  China, Shanghai, ChinaTelecom
12  61.152.24.81  301.42 ms  AS4812  China, Shanghai, ChinaTelecom
13  101.95.207.226  302.59 ms  AS4812  China, Shanghai, ChinaTelecom
14  101.227.255.34  303.08 ms  AS4812  China, Shanghai, ChinaTelecom
15  *
16  101.227.250.3  303.47 ms  AS4812  China, Shanghai, ChinaTelecom
17  *
18  *
19  180.153.28.1  302.46 ms  AS4812  China, Shanghai, ChinaTelecom
Traceroute to China, Guangzhou CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  67.199.141.33  7.84 ms  AS3257  United States, gtt.net
 6  141.136.110.41  240.62 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 7  154.14.32.238  262.26 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 8  202.97.52.93  293.61 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom
 9  *
10  *
11  113.108.209.1  290.57 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom
北京、上海联通回程
Traceroute to China, Beijing CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  67.199.141.33  0.42 ms  AS3257  United States, gtt.net
 6  213.200.117.138  239.80 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 7  *
 8  219.158.11.209  291.57 ms  AS4837  China, Guangdong, Guangzhou, ChinaUnicom
 9  219.158.111.213  313.80 ms  AS4837  China, Beijing, ChinaUnicom
10  219.158.115.121  305.23 ms  AS4837  China, Beijing, ChinaUnicom
11  219.158.16.81  300.30 ms  AS4837  China, Beijing, ChinaUnicom
12  *
13  *
14  124.65.194.122  312.97 ms  AS4808  China, Beijing, ChinaUnicom
15  124.65.194.138  311.98 ms  AS4808  China, Beijing, ChinaUnicom
16  *
17  *
18  123.125.99.1  354.80 ms  AS4808  China, Beijing, ChinaUnicom
Traceroute to China, Shanghai CU AS9929 (TCP Mode, Max 30 Hop)
============================================================
traceroute to 210.13.66.238 (210.13.66.238), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  *
 6  67.199.141.33  0.38 ms  AS3257  United States, gtt.net
 7  89.149.131.6  88.11 ms  AS3257  Singapore, gtt.net
 8  *
 9  38.142.239.114  266.22 ms  AS174  China, Shanghai, cogentco.com
10  38.142.239.114  264.33 ms  AS174  China, Shanghai, cogentco.com
11  218.105.2.198  271.74 ms  AS9929  China, Shanghai, ChinaUnicom
12  210.13.112.254  268.70 ms  AS9929  China, Shanghai, ChinaUnicom
13  *
14  210.13.64.109  270.45 ms  AS9929  China, Shanghai, ChinaUnicom
15  210.13.66.237  272.12 ms  AS9929  China, Shanghai, ChinaUnicom
16  210.13.66.237  267.25 ms  AS9929  China, Shanghai, ChinaUnicom
17  210.13.66.238  267.21 ms  AS9929  China, Shanghai, ChinaUnicom
北京、上海、广州移动回程
Traceroute to China, Beijing CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  67.199.141.33  0.42 ms  AS3257  United States, gtt.net
 6  89.149.181.102  248.20 ms  AS3257  United States, California, Los Angeles, gtt.net
 7  173.205.45.154  220.46 ms  AS3257  United States, California, Los Angeles, gtt.net
 8  173.205.45.154  220.14 ms  AS3257  United States, California, Los Angeles, gtt.net
 9  *
10  *
11  *
12  *
13  221.176.16.193  348.35 ms  AS9808  China, Beijing, ChinaMobile
14  111.24.2.134  350.89 ms  AS9808  China, Beijing, ChinaMobile
15  111.24.2.134  352.85 ms  AS9808  China, Beijing, ChinaMobile
16  *
17  211.136.63.66  359.68 ms  AS56048  China, Beijing, ChinaMobile
18  211.136.95.226  352.29 ms  AS56048  China, Beijing, ChinaMobile
19  *
20  211.136.25.153  361.35 ms  AS56048  China, Beijing, ChinaMobile
Traceroute to China, Shanghai CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 221.183.55.22 (221.183.55.22), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  *
 6  67.199.141.33  0.47 ms  AS3257  United States, gtt.net
 7  213.254.225.170  274.56 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 8  213.254.225.170  274.40 ms  AS3257  Germany, Hesse, Frankfurt, gtt.net
 9  223.120.10.85  272.02 ms  AS58453  Germany, Hesse, Frankfurt, ChinaMobile
10  *
11  *
12  221.183.55.22  342.49 ms  AS9808  China, Shanghai, ChinaMobile
Traceroute to China, Guangzhou CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 211.139.129.5 (211.139.129.5), 30 hops max, 32 byte packets
 1  *
 2  *
 3  *
 4  *
 5  67.199.141.33  15.59 ms  AS3257  United States, gtt.net
 6  213.200.119.34  229.11 ms  AS3257  gtt.net
 7  212.221.88.254  270.98 ms  AS3257  Europe Regions, gtt.net
 8  212.221.88.254  271.01 ms  AS3257  Europe Regions, gtt.net
 9  62.115.124.60  272.28 ms  AS1299  telia.com
10  62.115.47.45  273.13 ms  AS1299  Germany, Hesse, Frankfurt, telia.com
11  223.120.10.41  274.87 ms  AS58453  Germany, Hesse, Frankfurt, ChinaMobile
12  223.120.10.85  273.24 ms  AS58453  Germany, Hesse, Frankfurt, ChinaMobile
13  *
14  *
15  221.176.24.237  314.47 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
16  221.183.25.122  274.17 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
17  221.176.22.105  395.08 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
18  111.24.4.237  322.83 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
19  211.136.204.89  457.38 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
20  211.139.129.5  317.59 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile

八、UnixBench 跑分

Dhrystone 2 using register variables       44180435.6 lps   (10.0 s, 7 samples)
Double-Precision Whetstone                     3874.0 MWIPS (13.2 s, 7 samples)
Execl Throughput                               3454.1 lps   (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks        539722.5 KBps  (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks          140350.9 KBps  (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks       1788562.5 KBps  (30.0 s, 2 samples)
Pipe Throughput                              638144.5 lps   (10.0 s, 7 samples)
Pipe-based Context Switching                 146860.6 lps   (10.0 s, 7 samples)
Process Creation                              10865.7 lps   (30.0 s, 2 samples)
Shell Scripts (1 concurrent)                   5165.0 lpm   (60.0 s, 2 samples)
Shell Scripts (8 concurrent)                    702.1 lpm   (60.0 s, 2 samples)
System Call Overhead                         413155.1 lps   (10.0 s, 7 samples)

System Benchmarks Index Values               BASELINE       RESULT    INDEX
Dhrystone 2 using register variables         116700.0   44180435.6   3785.8
Double-Precision Whetstone                       55.0       3874.0    704.4
Execl Throughput                                 43.0       3454.1    803.3
File Copy 1024 bufsize 2000 maxblocks          3960.0     539722.5   1362.9
File Copy 256 bufsize 500 maxblocks            1655.0     140350.9    848.0
File Copy 4096 bufsize 8000 maxblocks          5800.0    1788562.5   3083.7
Pipe Throughput                               12440.0     638144.5    513.0
Pipe-based Context Switching                   4000.0     146860.6    367.2
Process Creation                                126.0      10865.7    862.4
Shell Scripts (1 concurrent)                     42.4       5165.0   1218.2
Shell Scripts (8 concurrent)                      6.0        702.1   1170.2
System Call Overhead                          15000.0     413155.1    275.4
                                                                   ========
System Benchmarks Index Score                                         941.8

九、总结

如果用来建站,而用户恰恰是大洋洲这边的,那么这款VPS非常适合你,无论是性能还是线路都是非常优秀的。但是对于国内用户来说,是非常不太适合的,可以用延迟中看出,国内延迟基本上都在200-300之间,卡出了翔,所以如果用户大部分在亚洲,那么站长更推荐你使用 Vultr韩国VPS或者日本VPS,在延迟方面都低于100,特别适合亚洲用户。

留下评论

您的电子邮箱地址不会被公开。 必填项已用*标注