kvmla:日本软银线路VPS测评(晚高峰),10M峰值带宽,支持Windows

2021年4月26日20:38:18 发表评论 656

kvmla:日本软银线路VPS测评(晚高峰),10M峰值带宽,支持Windows云服务器怎么样?云服务器值不值得购买?云服务器好不好?

kvmla:日本软银线路VPS测评(晚高峰),10M峰值带宽,支持Windows

kvmla是国内老品牌服务商(2011年运营至今),主营vps和独立服务器,数据中心包括,日本,中国香港,新加坡,洛杉矶以及多IP站群服务器。

这篇文章就来测评他们家的日本软银线路的vps,根据官方网站的描述VPS基于KVM虚拟,10Mbps峰值带宽(实际情况请看本文测试的真实带宽),线路混合了软银、ntt、kddi、cn2、iij,有windows可选择,不提供IPv6。

注意,商家支持三天无条件退款,但是严禁做各种违规业务

1、官网

网址:https://www.kvmla.pro

2、测评机器配置

VPS基于KVM虚拟,10Mbps峰值带宽,线路混合了软银、ntt、kddi、cn2、iij,有windows可选择,不提供IPv6。

日本机房有东京和大阪两个数据中心可以选择,本文的测评机器位于日本东京。

注意,标注红色的为今天的测评机器。这里的带宽是峰值10M,不过从下文的测评来看服务器带宽应该有100M。

月付八折优惠码:U20EY0GJR1

内存 CPU SSD 流量 带宽 价格 购买
2G 2核 30G 0.6T 10M 75元/月 链接
4G 4核 50G 0.8T 10M 145元/月 链接
6G 4核 80G 1.0T 10M 260元/月 链接

3、系统信息

cpu:e5,磁盘IO:304,看着这带宽测速,感觉至少有100M啊,官方写的峰值10M,会不会出错了?

4、杂项测试

媒体等

国内测速,这是晚高峰时段的测试,服务器带宽应该有100M

国外测速,欧美跑的也不错,带宽不止官方说的峰值10M。

 

FIO测试,这里的IO测试和上面的脚本得出的结果差不读~

 

5、路由测试

联通回程:

(1)北京、上海方向,机房出来就是软银,对接联通AS4837

(2)广州方向,机房出来就是NTT,对接联通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  23.186.64.1  0.37 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  0.92 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.39  0.49 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.50  4.22 ms  AS17675  Japan, Tokyo, inap.com
 5  203.105.72.201  2.04 ms  AS2914  Japan, Tokyo, ntt.com
 6  129.250.6.137  2.67 ms  AS2914  United States, ntt.com
 7  129.250.6.126  4.09 ms  AS2914  United States, ntt.com
 8  129.250.3.56  2.71 ms  AS2914  United States, ntt.com
 9  219.158.42.5  73.00 ms  AS4837  China, ChinaUnicom
10  219.158.103.33  79.21 ms  AS4837  China, ChinaUnicom
11  219.158.8.117  73.82 ms  AS4837  China, ChinaUnicom
12  120.83.0.62  73.00 ms  AS17816  China, Guangdong, Guangzhou, ChinaUnicom
13  120.80.79.194  73.65 ms  AS17622  China, Guangdong, Guangzhou, ChinaUnicom
14  *
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  23.186.64.1  0.38 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  1.00 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.40  0.42 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.113  1.70 ms  AS17675  Japan, Tokyo, inap.com
 5  101.102.204.253  1.92 ms  AS17676  Japan, Tokyo, bbtec.net
 6  *
 7  *
 8  *
 9  221.111.202.14  35.75 ms  AS17676  Japan, bbtec.net
10  219.158.113.138  56.50 ms  AS4837  China, ChinaUnicom
11  219.158.113.109  53.32 ms  AS4837  China, ChinaUnicom
12  *
13  139.226.228.46  51.02 ms  AS17621  China, Shanghai, ChinaUnicom
14  139.226.225.22  53.25 ms  AS17621  China, Shanghai, ChinaUnicom
15  58.247.8.153  59.18 ms  AS17621  China, Shanghai, ChinaUnicom
16  *
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  23.186.64.1  0.37 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  1.29 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.39  0.59 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.49  1.51 ms  AS17675  Japan, Tokyo, inap.com
 5  101.102.204.253  1.64 ms  AS17676  Japan, Tokyo, bbtec.net
 6  *
 7  *
 8  *
 9  221.111.202.70  52.23 ms  AS17676  Japan, bbtec.net
10  219.158.3.49  48.83 ms  AS4837  China, ChinaUnicom
11  219.158.4.169  53.25 ms  AS4837  China, ChinaUnicom
12  125.33.186.26  50.06 ms  AS4808  China, Beijing, ChinaUnicom
13  61.148.156.238  52.02 ms  AS4808  China, Beijing, ChinaUnicom
14  124.65.194.138  53.11 ms  AS4808  China, Beijing, ChinaUnicom
15  61.135.113.158  52.33 ms  AS4808  China, Beijing, ChinaUnicom
16  *
17  *
18  123.125.99.1  51.57 ms  AS4808  China, Beijing, ChinaUnicom

联通去程,169对接软银,最后到inap机房:

电信回程,路由被隐藏了吧,不过看最后的11跳只用了63ms,所以肯定没有绕道。

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  23.186.64.1  0.40 ms  AS49466  Japan, Tokyo, klayer.com
 2  *
 3  *
 4  *
 5  *
 6  *
 7  *
 8  *
 9  36.110.244.46  65.34 ms  AS23724  China, Beijing, ChinaTelecom
10  36.110.246.198  66.18 ms  AS23724  China, Beijing, ChinaTelecom
11  180.149.128.9  63.89 ms  AS23724  China, Beijing, 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  23.186.64.1  0.40 ms  AS49466  Japan, Tokyo, klayer.com
 2  *
 3  *
 4  *
 5  *
 6  *
 7  61.152.24.190  35.96 ms  AS4812  China, Shanghai, ChinaTelecom
 8  101.95.206.18  38.15 ms  AS4812  China, Shanghai, ChinaTelecom
 9  101.95.225.34  38.82 ms  AS4811  China, Shanghai, ChinaTelecom
10  101.227.255.34  37.50 ms  AS4812  China, Shanghai, ChinaTelecom
11  180.153.28.5  37.63 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  23.186.64.1  0.34 ms  AS49466  Japan, Tokyo, klayer.com
 2  *
 3  *
 4  *
 5  *
 6  *
 7  *
 8  202.97.19.178  59.99 ms  AS4134  China, ChinaTelecom
 9  113.108.209.1  57.15 ms  AS58466  China, Guangdong, Guangzhou, ChinaTelecom

电信去程,163对接软银。

移动回程

(1)北京和广州方向是软银回程,(2)上海方向是KDDI回程

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  23.186.64.1  0.30 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  1.23 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.39  0.53 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.113  1.55 ms  AS17675  Japan, Tokyo, inap.com
 5  101.102.204.253  1.60 ms  AS17676  Japan, Tokyo, bbtec.net
 6  *
 7  *
 8  *
 9  *
10  223.120.2.117  50.19 ms  AS58453  China, ChinaMobile
11  *
12  *
13  221.183.52.85  56.24 ms  AS9808  China, ChinaMobile
14  221.176.22.105  56.53 ms  AS9808  China, ChinaMobile
15  *
16  111.24.14.86  59.44 ms  AS9808  China, ChinaMobile
17  211.136.208.33  61.83 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
18  211.139.180.106  63.36 ms  AS56040  China, Guangdong, Guangzhou, ChinaMobile
19  *
20  *
21  120.196.212.25  58.70 ms  AS56040  China, Guangdong, Guangzhou, 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  23.186.64.1  0.34 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  1.53 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.106  0.41 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.95  1.36 ms  AS17675  Japan, Tokyo, inap.com
 5  124.211.14.61  1.66 ms  AS2516  Japan, Tokyo, kddi.com
 6  27.85.137.237  1.87 ms  AS2516  Japan, Tokyo, kddi.com
 7  106.187.14.6  1.76 ms  AS2516  Japan, Tokyo, kddi.com
 8  106.187.14.122  59.52 ms  AS2516  China, Hong Kong, kddi.com
 9  111.87.5.110  50.04 ms  AS2516  China, Hong Kong, kddi.com
10  *
11  223.120.2.57  148.63 ms  AS58453  China, ChinaMobile
12  *
13  *
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  23.186.64.1  0.35 ms  AS49466  Japan, Tokyo, klayer.com
 2  210.193.120.225  0.93 ms  AS17675  Japan, Tokyo, inap.com
 3  61.211.160.106  0.38 ms  AS17675  Japan, Tokyo, inap.com
 4  61.211.160.113  1.53 ms  AS17675  Japan, Tokyo, inap.com
 5  101.102.204.253  1.57 ms  AS17676  Japan, Tokyo, bbtec.net
 6  *
 7  *
 8  221.111.202.126  2.27 ms  AS17676  Japan, bbtec.net
 9  *
10  *
11  *
12  *
13  111.24.2.241  88.89 ms  AS9808  China, ChinaMobile
14  *
15  *
16  211.136.63.66  93.30 ms  AS56048  China, Beijing, ChinaMobile
17  211.136.63.66  93.12 ms  AS56048  China, Beijing, ChinaMobile
18  *
19  *
20  *
21  211.136.25.153  90.33 ms  AS56048  China, Beijing, ChinaMobile

移动去程,移动骨干走香港CMI出口转软银到日本机房

6、路由掉包

晚高峰测试:22点—22点30分,看着还可以,特别红的那两个应该是接点挂了。

7、全国ping

8、Geekbench 5 Benchmark Test

单核:542,双核:1058

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

9、最后

线路总结:从回程的数据来看,不是单纯的纯软银,而是软银混合了NTT、KDDI、iij组成的BGP线路。去程走的是国内骨干对接到软银。

机器性能,中规中矩,但用来建站肯定是没问题的。

网络测试:

  • 香港将军澳:hk1.kvmla.pro
  • 香港沙田:hk2.kvmla.pro
  • 新加坡:sg1.kvmla.pro
  • 日本东京:tky1.kvmla.pro
  • 1、官网
  • 2、测评机器配置
  • 3、系统信息
  • 4、杂项测试
  • 5、路由测试
  • 6、路由掉包
  • 7、全国ping
  • 8、Geekbench 5 Benchmark Test
  • 9、最后

kvmla:日本软银线路VPS测评(晚高峰),10M峰值带宽,支持Windows

来源链接:https://www.vpssz.com/

本站声明:网站内容来源于网络,如有侵权,请联系我们,我们将及时处理。

郑重声明:VPS主机评测仅提供资料收集及VPS云主机信息推介,不提供任何VPS云主机及代购业务!