感谢小伙伴HankChow提供测试机器，购买链接中包含了其 AFF。
总的来说算是一个十分低价的日本流媒体/游戏解锁方案。
买
OVZ 款
最低低至 450 日元/月，单个实例最多可附加 5 个 IP，每个 IP 500 日元/月
https://support.1strentalserver.com/aff.php?aff=184&gid=4
KVM 款
最低低至 1000 日元/月，单个实例最多可附加 256 个 IP，每个 IP 500 日元/月（ovz over kvm!）
https://support.1strentalserver.com/aff.php?aff=184&gid=5
测
LemonBench
系统详情
-> System Information
OS Release: CentOS Linux 7.2.1511 (x86_64)
CPU Model: Intel Core Processor (Haswell, no TSX, IBRS) 0.87 GHz
CPU Cache Size: 4096 KB
CPU Number: 2 vCPU (24 Host Core/Thread)
Virt Type: OpenVZ
Memory Usage: 36.04 MB / 2.00 GB
Swap Usage: 0 KB / 2.00 GB
Boot Device: /dev/ploop14169p1
Disk Usage: 61.79 GB / 0.01 GB
CPU Usage: 6.3% used, 0.0% iowait, 0.0% steal
Load (1/5/15min): 0.00 0.03 0.05
Uptime: 0 Days, 0 Hours, 14 Minutes, 40 Seconds
Kernel Version: 3.10.0-1127.8.2.vz7.158.8
Network CC Method: +
-> Network Infomation
IPV4 - IP Address: [JP] 210.149.68.*
IPV4 - ASN Info: AS2497 (IIJ - Internet Initiative Japan Inc., JP)
IPV4 - Region: Japan Fukuoka
硬件测试
-> CPU Performance Test (Fast Mode, 1-Pass @ 5sec)
1 Thread Test: 548 Scores
2 Threads Test: 545 Scores
-> Memory Performance Test (Fast Mode, 1-Pass @ 5sec)
1 Thread - Read Test : 12165.97 MB/s
1 Thread - Write Test: 8475.82 MB/s
-> Disk Speed Test (4K Block/1M Block, Direct Mode)
Test Name Write Speed Read Speed
100MB-4K Block 601 MB/s (0.01K IOPS, 0.17s) ->bash:行1154: /proc/sys/vm/drop_caches: 权限不够
100MB-4K Block 601 MB/s (0.01 IOPS, 0.17s) 1.4 GB/秒 (345341 IOPS, 0.07s)
1GB-1M Block 557 MB/s (531 IOPS, 1.88s) ->bash:行1154: /proc/sys/vm/drop_caches: 权限不够
1GB-1M Block 557 MB/s (531 IOPS, 1.88s) 2.0 GB/秒 (1953 IOPS, 0.51s)
Traceroute
北京联通
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 202.214.49.68 0.20 ms AS2497 Japan, Fukuoka, iij.ad.jp
2 210.130.147.57 11.36 ms AS2497 Japan, Fukuoka, iij.ad.jp
3 58.138.119.41 1.65 ms AS2497 Japan, iij.ad.jp
4 58.138.89.134 14.83 ms AS2497 Japan, iij.ad.jp
5 58.138.88.69 21.17 ms AS2497 Japan, Tokyo, iij.ad.jp
6 58.138.112.54 21.24 ms AS2497 Japan, Tokyo, iij.ad.jp
7 *
8 219.158.30.69 60.80 ms AS4837 China, ChinaUnicom
9 219.158.19.74 54.55 ms AS4837 China, Shanghai, ChinaUnicom
10 219.158.19.81 55.44 ms AS4837 China, Shanghai, ChinaUnicom
11 *
12 *
13 124.65.63.38 71.76 ms AS4808 China, Beijing, ChinaUnicom
14 124.65.194.138 81.92 ms AS4808 China, Beijing, ChinaUnicom
15 61.135.113.158 69.50 ms AS4808 China, Beijing, ChinaUnicom
16 *
17 123.125.99.1 79.59 ms AS4808 China, Beijing, ChinaUnicom
北京电信
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 202.214.49.68 0.20 ms AS2497 Japan, Fukuoka, iij.ad.jp
2 210.130.147.57 15.18 ms AS2497 Japan, Fukuoka, iij.ad.jp
3 58.138.119.41 1.69 ms AS2497 Japan, iij.ad.jp
4 58.138.89.134 33.64 ms AS2497 Japan, iij.ad.jp
5 58.138.88.69 23.52 ms AS2497 Japan, Tokyo, iij.ad.jp
6 58.138.112.54 30.90 ms AS2497 Japan, Tokyo, iij.ad.jp
7 203.215.237.13 19.98 ms * Japan, Tokyo, ChinaTelecom
8 202.97.43.133 54.52 ms AS4134 China, Shaanxi, Xi'an, ChinaTelecom
9 *
10 202.97.24.205 62.91 ms AS4134 China, Shanghai, ChinaTelecom
11 *
12 *
13 *
14 180.149.128.9 75.53 ms AS23724 China, Beijing, ChinaTelecom
北京移动
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 202.214.49.68 0.19 ms AS2497 Japan, Fukuoka, iij.ad.jp
2 210.130.147.57 4.12 ms AS2497 Japan, Fukuoka, iij.ad.jp
3 58.138.119.41 1.81 ms AS2497 Japan, iij.ad.jp
4 58.138.89.134 15.91 ms AS2497 Japan, iij.ad.jp
5 58.138.88.69 20.99 ms AS2497 Japan, Tokyo, iij.ad.jp
6 58.138.114.222 21.51 ms AS2497 Japan, Tokyo, iij.ad.jp
7 202.232.8.190 21.24 ms AS2497 Japan, Tokyo, iij.ad.jp
8 *
9 *
10 *
11 *
12 111.24.17.158 114.26 ms AS9808 China, Beijing, ChinaMobile
13 *
14 *
15 *
16 211.136.67.166 110.95 ms AS56048 China, Beijing, ChinaMobile
17 211.136.95.226 115.94 ms AS56048 China, Beijing, ChinaMobile
18 *
19 *
20 211.136.25.153 121.29 ms AS56048 China, Beijing, ChinaMobile
上海联通 AS9929
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 202.214.49.68 0.18 ms AS2497 Japan, Fukuoka, iij.ad.jp
2 210.130.147.57 6.48 ms AS2497 Japan, Fukuoka, iij.ad.jp
3 58.138.119.33 1.60 ms AS2497 Japan, iij.ad.jp
4 58.138.89.130 12.75 ms AS2497 Japan, iij.ad.jp
5 58.138.88.65 19.21 ms AS2497 Japan, Tokyo, iij.ad.jp
6 58.138.112.138 19.89 ms AS2497 Japan, Tokyo, iij.ad.jp
7 *
8 219.158.16.49 50.62 ms AS4837 China, Shanghai, ChinaUnicom
9 219.158.39.210 53.59 ms AS4837 China, Hubei, Wuhan, ChinaUnicom
10 218.105.2.93 48.33 ms AS9929 China, Shanghai, ChinaUnicom
11 *
12 210.13.116.82 51.16 ms AS9929 China, Shanghai, ChinaUnicom
13 210.13.64.109 63.97 ms AS9929 China, Shanghai, ChinaUnicom
14 210.13.64.110 50.14 ms AS9929 China, Shanghai, ChinaUnicom
15 210.13.66.237 62.00 ms AS9929 China, Shanghai, ChinaUnicom
16 210.13.66.238 58.24 ms AS9929 China, Shanghai, ChinaUnicom
上海电信 CN2
Traceroute to China, Shanghai CT CN2 (TCP Mode, Max 30 Hop)
============================================================
traceroute to 58.32.0.1 (58.32.0.1), 30 hops max, 32 byte packets
1 202.214.49.68 0.46 ms AS2497 Japan, Fukuoka, iij.ad.jp
2 210.130.147.57 2.00 ms AS2497 Japan, Fukuoka, iij.ad.jp
3 58.138.119.41 1.21 ms AS2497 Japan, iij.ad.jp
4 58.138.89.142 19.56 ms AS2497 Japan, iij.ad.jp
5 58.138.107.22 19.40 ms AS2497 Japan, Osaka, iij.ad.jp
6 210.173.179.33 16.10 ms * Japan, Tokyo, mfeed.ad.jp
7 129.250.7.30 55.93 ms AS2914 Japan, Osaka, ntt.com
8 129.250.7.78 68.42 ms AS2914 Japan, Tokyo, ntt.com
9 129.250.6.133 25.29 ms AS2914 Japan, Tokyo, ntt.com
10 117.103.177.106 25.69 ms AS2914 Japan, Tokyo, ntt.com
11 120.88.54.134 24.11 ms AS2914 Japan, Tokyo, ntt.com
12 *
13 *
14 *
15 58.32.0.1 79.20 ms AS4812 China, Shanghai, ChinaTelecom
流媒体解锁测试
最后的小咪咪🐶
如果有日本流媒体需求，又恰逢预算有限可以考虑购买 KVM 款。
请注意不要尝试自行 DD 系统，建议与客服工单沟通（1-2 天处理工单）。
最后再次感谢小伙伴提供测试机器~
评论区