Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

2022年4月13日10:42:47VPS评测57,971阅读模式

Virmach的日本预售VPS终于开机了,足足苦等了一个月,服务器位于日本东京,默认1Gbps带宽,根据官方的说法是接入IIJ、level3等混合线路。这篇文章就来测评分享该VPS性能数据,想了解virmach日本怎么样的童鞋可以围观。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

1、官网

官方网站https://virmach.com/

 

2、AMD Ryzen+NVMe系列VPS促销

特征:KVM虚拟,CPU是AMD Ryzen,磁盘NVMe阵列,1G带宽,自带一个IPv4

可选机房:目前可选东京,西雅图和圣何塞,其他机房如洛杉矶、阿姆斯特丹、水牛城、达拉斯、亚特兰大、凤凰城、芝加哥还在准备中。

注意,标注红色文字的为今天的测评机器,预售是这款机器是年付$12.17

CPU 内存 NVMe 月流量 价格 购买
1核 768M 20G 2T $30/2年 链接
1核 1.5G 35G 4T $40/2年 链接
2核 2.5G 50G 6T $50/2年 链接
3核 4.0G 80G 8T $70/2年 链接

 

3、系统信息

CPU:AMD Ryzen 9 5900X 12-Core,磁盘io:868.7 MB/s

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

4、杂项测试

流媒体测试,这个IP拉胯了点,自己斟酌吧。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

国内测速,默认是1Gbps带宽,因为开机时间较晚,所以现在这个国内三网节点已经不咋地了。这还是大白天的测试结果,如果晚高峰估计效果会更差点,等晚高峰在测试看看效果。Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

国内三网晚高峰测试结果:晚高峰的测试结果很不好,移动还说得过去,其他的就拉跨的很了。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

国外测速,欧美测速真是拉胯的很。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

磁盘FIO,磁盘的读写测试,还是很不错的。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

5、路由测试

电信回程,走iij,国内部分走电信163,直连。

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  45.66.128.1  26.95 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  20.17 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  24.31 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.178  0.70 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.69  22.35 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  124.147.2.1  0.65 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 7  210.138.130.225  1.02 ms  AS2497  Japan, Tokyo, iij.ad.jp
 8  58.138.98.73  1.51 ms  AS2497  Japan, Tokyo, iij.ad.jp
 9  58.138.112.50  1.48 ms  AS2497  Japan, Tokyo, iij.ad.jp
10  203.215.237.13  3.13 ms  *  Japan, Tokyo, ChinaTelecom
11  202.97.43.5  54.00 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom
12  *
13  202.97.94.137  54.16 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom
14  113.108.209.1  53.83 ms  AS4134  China, Guangdong, Guangzhou, ChinaTelecom


Traceroute to China, Shanghai CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 32 byte packets
 1  45.66.128.1  2.47 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  50.56 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  19.58 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.222  0.45 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.77  1.00 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  124.147.2.1  2.67 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 7  210.138.130.225  1.26 ms  AS2497  Japan, Tokyo, iij.ad.jp
 8  58.138.98.73  3.10 ms  AS2497  Japan, Tokyo, iij.ad.jp
 9  58.138.112.50  1.96 ms  AS2497  Japan, Tokyo, iij.ad.jp
10  203.215.237.13  2.46 ms  *  Japan, Tokyo, ChinaTelecom
11  202.97.41.141  28.82 ms  AS4134  China, Shanghai, ChinaTelecom
12  202.97.12.185  35.51 ms  AS4134  China, Shanghai, ChinaTelecom
13  *
14  61.152.25.85  77.34 ms  AS4812  China, Shanghai, ChinaTelecom
15  101.95.207.18  64.21 ms  AS4812  China, Shanghai, ChinaTelecom
16  124.74.232.58  91.10 ms  AS4811  China, Shanghai, ChinaTelecom
17  101.227.255.46  49.33 ms  AS4812  China, Shanghai, ChinaTelecom
18  180.153.28.5  96.37 ms  AS4812  China, Shanghai, ChinaTelecom


Traceroute to China, Beijing CT (TCP Mode, Max 30 Hop)
============================================================
traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 32 byte packets
 1  45.66.128.1  1.85 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  9.39 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  32.09 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.178  0.80 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.77  1.19 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  124.147.2.1  1.17 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 7  210.138.130.225  1.10 ms  AS2497  Japan, Tokyo, iij.ad.jp
 8  58.138.98.73  4.66 ms  AS2497  Japan, Tokyo, iij.ad.jp
 9  58.138.112.138  59.93 ms  AS2497  Japan, Tokyo, iij.ad.jp
10  203.215.237.13  2.28 ms  *  Japan, Tokyo, ChinaTelecom
11  *
12  *
13  202.97.62.97  35.94 ms  AS4134  China, Shanghai, ChinaTelecom
14  202.97.33.97  51.23 ms  AS4134  China, Beijing, ChinaTelecom
15  *
16  36.110.246.214  125.54 ms  AS23724  China, Beijing, ChinaTelecom
17  180.149.128.9  50.93 ms  AS23724  China, Beijing, ChinaTelecom

电信去程,还是走的iij,直连!!

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

联通回程,走的iij,绕美国走的level3,国内部分走的联通as4837!!

Traceroute to China, Guangzhou CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 32 byte packets
 1  45.66.128.1  6.47 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  10.73 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  0.58 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.222  2.64 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.69  0.57 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  172.25.0.9  14.30 ms  *  LAN Address
 7  *
 8  4.69.153.125  110.30 ms  AS3356  United States, California, Los Angeles, level3.com
 9  4.26.1.134  168.62 ms  AS3356  United States, California, Los Angeles, level3.com
10  219.158.96.29  174.87 ms  AS4837  China, Guangdong, Guangzhou, ChinaUnicom
11  219.158.20.221  171.26 ms  AS4837  China, Guangdong, Guangzhou, ChinaUnicom
12  219.158.24.125  175.77 ms  AS4837  China, Guangdong, Guangzhou, ChinaUnicom
13  120.83.0.62  177.10 ms  AS17816  China, Guangdong, Guangzhou, ChinaUnicom
14  120.80.175.62  168.50 ms  AS17622  China, Guangdong, Guangzhou, ChinaUnicom
15  *
16  *
17  *

Traceroute to China, Shanghai CU (TCP Mode, Max 30 Hop)
============================================================
traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 32 byte packets
 1  45.66.128.1  64.65 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  12.06 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  12.48 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.178  1.38 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.69  66.47 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  172.25.0.9  19.14 ms  *  LAN Address
 7  *
 8  4.69.209.169  104.91 ms  AS3356  United States, California, San Jose, level3.com
 9  4.53.208.102  152.97 ms  AS3356  United States, California, San Jose, level3.com
10  219.158.104.109  137.97 ms  AS4837  China, Shanghai, ChinaUnicom
11  219.158.19.86  139.10 ms  AS4837  China, Shanghai, ChinaUnicom
12  219.158.19.69  134.46 ms  AS4837  China, Shanghai, ChinaUnicom
13  139.226.231.106  168.71 ms  AS17621  China, Shanghai, ChinaUnicom
14  58.247.221.178  137.25 ms  AS17621  China, Shanghai, ChinaUnicom
15  139.226.225.22  159.03 ms  AS17621  China, Shanghai, ChinaUnicom
16  58.247.8.153  147.81 ms  AS17621  China, Shanghai, ChinaUnicom
17  *
18  *
19  *
20  *

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  45.66.128.1  1.16 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  2.45 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  1.66 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.222  30.20 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.69  16.94 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  172.25.0.9  0.55 ms  *  LAN Address
 7  *
 8  *
 9  4.26.2.118  164.98 ms  AS3356  United States, California, Los Angeles, level3.com
10  219.158.16.93  170.31 ms  AS4837  China, Beijing, ChinaUnicom
11  219.158.9.214  169.71 ms  AS4837  China, Beijing, ChinaUnicom
12  *
13  61.49.214.10  169.56 ms  AS4808  China, Beijing, ChinaUnicom
14  61.148.159.30  206.58 ms  AS4808  China, Beijing, ChinaUnicom
15  124.65.194.134  166.53 ms  AS4808  China, Beijing, ChinaUnicom
16  61.135.113.154  195.74 ms  AS4808  China, Beijing, ChinaUnicom
17  *
18  123.125.99.1  171.56 ms  AS4808  China, Beijing, ChinaUnicom

群里的一些大佬也测试了路由,如果联通走level3就是绕美了,不过联通应该大部分都是直连,这张图是群里的截图。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

联通去程,走的iij,直连。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

移动回程,走的level3,直连。看来移动测试太多了被限制了,都403了。

Traceroute to China, Guangzhou CM (TCP Mode, Max 30 Hop)
============================================================
traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 32 byte packets
 1  45.66.128.1  1.27 ms  AS23959  Japan, Tokyo, xtom.com
 2  45.149.159.1  7.17 ms  AS23959  Japan, Tokyo, xtom.com
 3  91.200.240.5  0.97 ms  AS23959  Japan, Tokyo, xtom.com
 4  211.14.4.222  19.78 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 5  124.147.3.69  64.89 ms  AS9607  Japan, Tokyo, bbtower.co.jp
 6  172.25.0.9  65.46 ms  *  LAN Address
 7  *
 8  4.69.218.122  76.84 ms  AS3356  Japan, Tokyo, level3.com
 9  4.68.38.226  1.98 ms  AS3356  Japan, Tokyo, level3.com
10  223.120.2.189  2.36 ms  AS58453  Japan, Tokyo, ChinaMobile
11  223.120.2.21  113.18 ms  AS58453  China, Hong Kong, ChinaMobile
12  *
13  221.183.55.74  64.34 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
14  221.183.25.118  59.49 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
15  221.176.22.157  78.36 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
16  111.24.4.233  86.07 ms  AS9808  China, Guangdong, Guangzhou, ChinaMobile
17  111.24.5.34  127.85 ms  http: 403  http: 403
18  211.136.249.109  64.99 ms  http: 403  http: 403
19  211.139.180.110  66.84 ms  http: 403  http: 403
20  *
21  *
22  *
23  120.196.212.25  102.76 ms  http: 403  http: 403


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  45.66.128.1  15.55 ms  http: 403  http: 403
 2  45.149.159.1  6.98 ms  http: 403  http: 403
 3  91.200.240.5  1.32 ms  http: 403  http: 403
 4  211.14.4.222  10.26 ms  http: 403  http: 403
 5  124.147.3.77  0.73 ms  http: 403  http: 403
 6  172.25.0.1  1.13 ms  http: 403  http: 403
 7  202.127.69.134  1.65 ms  http: 403  http: 403
 8  134.159.125.201  1.90 ms  http: 403  http: 403
 9  223.118.4.241  1.79 ms  http: 403  http: 403
10  223.120.3.81  7.66 ms  http: 403  http: 403
11  *
12  221.183.55.22  62.88 ms  http: 403  http: 403


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  45.66.128.1  7.13 ms  http: 403  http: 403
 2  45.149.159.1  6.91 ms  http: 403  http: 403
 3  91.200.240.5  1.09 ms  http: 403  http: 403
 4  211.14.4.178  1.02 ms  http: 403  http: 403
 5  124.147.3.69  35.38 ms  http: 403  http: 403
 6  172.25.0.1  0.81 ms  http: 403  http: 403
 7  202.127.69.134  1.85 ms  http: 403  http: 403
 8  134.159.125.201  2.02 ms  http: 403  http: 403
 9  *
10  *
11  *
12  221.176.27.253  74.69 ms  http: 403  http: 403
13  111.24.2.97  103.48 ms  http: 403  http: 403
14  111.24.14.54  74.29 ms  http: 403  http: 403
15  *
16  *
17  211.136.95.226  107.66 ms  http: 403  http: 403
18  *
19  *
20  *
21  211.136.25.153  78.69 ms  http: 403  http: 403

移动去程,走的移动cmi+iij,直连。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

6、路由掉包

非晚高峰测试,仅供参考:

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

7、ping

全国177个节点的测试结果,仅供参考。

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

8、Geekbench 5 Benchmark Test

单核:897分,性能不错。

详细:https://browser.geekbench.com/v5/cpu/14279291

Virmach日本东京机房的VPS(AMD+NVMe SSD)测评分享

9、最后

机器性能:因为是AMD+NVMe SSD,性能上面还是很不错的。

线路总结:

电信双程直连,都是走的iij。

联通部分地区走level3,绕美。绝大部分地区都是双程直连,走iij。

移动双程直连,回程走level3或者telstra等等,去程还是走的cmi+iij。

因为是iij混合线路,所以部分地区的测试结果有差异,所以最好自己测试下,看看是不是适合自己的。

weinxin
微信公众号
关注大鸟博客公众号
大鸟
评论  5  访客  4  作者  1
    • 545040
      545040 3

      幸好没入,感觉不咋地

      • 橘猫
        橘猫 1

        买了个2年付的,总体来说还是不错的,油管白天7W左右,晚上也有2W左右,坐标江苏电信.

          • 大鸟
            大鸟

            @ 橘猫 我也用了下,发现也还行,和你说的差不多,也是电信!!

            • 蓝盾
              蓝盾 0

              @ 橘猫 晚高峰掉包率怎么样?

                • Anchep
                  Anchep 0

                  @ 蓝盾 晚高峰丢包受不了

            匿名

            发表评论

            匿名网友

            :?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

            确定