Description: There are many current VPS
testing scripts, but the testing items are not very comprehensive. Therefore, the great master Qianying has rewritten a brand new Linux VPS
testing script based on many testing scripts. The biggest feature of this script is its comprehensive testing, rapid execution, and it will not cause long testing times due to low disk i/o
or poor network conditions. Regardless of the machine, it can be executed quickly without UnixBench
, and the results can be shared via the web after testing.
Testing Items#
- Obtain basic system information
- Test disk access latency,
iops
, access speed - Test local bandwidth
- Test download speed from the local machine to
25
foreign nodes - Test download speed from the local machine to
8
domestic nodes - Test routing from the local machine to
9
domestic nodes - Test latency and packet loss from the local machine to
9
domestic nodes
Usage#
1. Download the script
wget -N --no-check-certificate https://raw.githubusercontent.com/chiakge/Linux-Server-Bench-Test/master/linuxtest.sh
2. Use commands
# Test without UnixBench, no web sharing
bash linuxtest.sh
# Test without UnixBench, with web sharing
bash linuxtest.sh s
# Test with UnixBench, no web sharing
bash linuxtest.sh a
# Test with UnixBench, with web sharing
bash linuxtest.sh as
Test Sample#
========== Start recording test information ==========
Test time: 2018-05-15 18:06:27
----------------------------------------------------------------------
CPU model : Virtual CPU a7769a6388d5
Number of cores : 1
CPU frequency : 2394.454 MHz
Total size of Disk : 20.2 GB (4.7 GB Used)
Total amount of Mem : 492 MB (107 MB Used)
Total amount of Swap : 1023 MB (4 MB Used)
System uptime : 2 days, 20 hour 0 min
Load average : 0.65, 0.18, 0.06
OS : Debian GNU/Linux 9
Arch : x86_64 (64 Bit)
Kernel : 4.9.0-5-amd64
ip : 108.61.126.101
ipaddr : Japan Tokyo Tokyo choopa.com
vm : kvm
----------------------------------------------------------------------
===== Start disk performance test =====
ioping: seek rate
min/avg/max/mdev = 197.8 us / 337.5 us / 5.84 ms / 142.6 us
ioping: sequential speed
generated 2.84 k requests in 5.00 s, 709.8 MiB, 567 iops, 141.9 MiB/s
===== Disk performance test completed =====
----------------------------------------------------------------------
===== Start speedtest =====
Retrieving speedtest.net configuration...
Testing from Choopa, LLC (108.61.*.*)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by cloudremix (Tokyo) [12.58 km]: 4.648 ms
Testing download speed................................................................................
Download: 764.43 Mbit/s
Testing upload speed................................................................................................
Upload: 139.42 Mbit/s
Share results: http://www.speedtest.net/result/7310913596.png
===== speedtest completed =====
----------------------------------------------------------------------
Node Name: IPv4 address: Download Speed
CacheFly: 204.93.150.152: 102.64 MiB/s 821.10 Mbps
Linode, Tokyo, JP: 106.187.96.148: 36.95 MiB/s 295.59 Mbps
Linode, Tokyo2, JP: 139.162.65.37: 76.18 MiB/s 609.43 Mbps
Linode, Singapore, SG: 139.162.23.4: 16.44 MiB/s 131.48 Mbps
Linode, Fremont, CA: 50.116.14.9: 277.89 KiB/s 2.17 Mbps
Linode, Newark, NJ: 50.116.57.237: 7.84 MiB/s 62.71 Mbps
Linode, London, UK: 176.58.107.39: 6.27 MiB/s 50.20 Mbps
Linode, Frankfurt, DE: 139.162.130.8: 5.66 MiB/s 45.27 Mbps
Softlayer, Tokyo, JP: 161.202.125.20: 130.64 MiB/s 1045.14 Mbps
Softlayer, Singapore, SG: 119.81.28.170: 469.33 KiB/s 3.67 Mbps
Softlayer, Seoul, KR: 119.81.28.170: 495.91 KiB/s 3.87 Mbps
Softlayer, HongKong, CN: 119.81.130.170: 374.38 KiB/s 2.92 Mbps
Softlayer, Dallas, TX: 169.48.124.82: 1.55 MiB/s 12.37 Mbps
Softlayer, Seattle, WA: 67.228.112.250: 301.42 KiB/s 2.35 Mbps
Softlayer, Frankfurt, DE: 159.122.69.4: 472.46 KiB/s 3.69 Mbps
Softlayer, Paris, FR: 159.8.64.212: 271.49 KiB/s 2.12 Mbps
Leaseweb, HongKong, CN: 43.249.36.49: 2.09 MiB/s 16.71 Mbps
Leaseweb, Singapore, SG: 103.254.153.18: 288.60 KiB/s 2.25 Mbps
Leaseweb, Washington D.C., US: 207.244.94.80: 146.71 KiB/s 1.15 Mbps
Leaseweb, San Francisco, US: 209.58.135.187: 464.09 KiB/s 3.63 Mbps
Leaseweb, Netherlands, NL: 5.79.108.33: 149.20 KiB/s 1.17 Mbps
OVH, Montreal, CA: 192.99.19.165: 1.04 MiB/s 8.34 Mbps
ChinaTelecom, Shanghai, CN: 101.95.48.41: 193.00 KiB/s 1.51 Mbps
ChinaTelecom, Beijing, CN: 60.247.96.2: 341.15 KiB/s 2.67 Mbps
ChinaUnicom, Beijing, CN: 61.135.202.2: 2.46 MiB/s 19.72 Mbps
ChinaTelecom, Guangzhou, CN: 119.145.88.166: 383.05 KiB/s 2.99 Mbps
ChinaMobile, Guangzhou, CN: 221.179.46.222: 960.18 KiB/s 7.50 Mbps
ChinaTelecom, Hefei, CN: 61.191.111.11: 290.96 KiB/s 2.27 Mbps
ChinaUnicom, Hefei, CN: 112.122.10.26: 1.71 MiB/s 13.65 Mbps
ChinaMobile, Hefei, CN: 120.209.140.60: 790.67 KiB/s 6.18 Mbps
Hinet, Taiwan, TW: 210.61.132.1: 6.43 MiB/s 51.41 Mbps
----------------------------------------------------------------------
===== Testing [Sichuan Telecom] return route =====
traceroute to 125.64.38.178 (125.64.38.178), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 19.72 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 1.09 ms AS20473 Japan Tokyo Tokyo choopa.com
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 2.61 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.6.188) 2.08 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-4.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.3.57) 1.93 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-10.r26.tokyjp05.jp.bb.gin.ntt.net (129.250.2.152) 1.81 ms AS2914 Japan Tokyo Tokyo ntt.com
8 202.97.51.61 85.03 ms AS4134 China Shanghai Telecom
9 202.97.90.58 83.64 ms AS4134 China Shanghai Telecom
10 202.97.57.230 86.66 ms AS4134 China Shanghai Telecom
11 202.97.36.2 134.01 ms AS4134 China Sichuan Chengdu Telecom
12 *
13 118.123.217.86 134.36 ms AS38283 China Sichuan Chengdu Telecom
14 118.123.214.38 131.01 ms AS38283 China Sichuan Chengdu Telecom
15 125.64.38.178 129.30 ms AS38283 China Sichuan Chengdu Telecom
===== Return [Sichuan Telecom] route test completed =====
===== Testing [Beijing Telecom] return route =====
traceroute to 106.120.243.142 (106.120.243.142), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 16.77 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 0.97 ms AS20473 Japan Tokyo Tokyo choopa.com
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 62.23 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.6.188) 2.17 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-4.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.3.57) 2.00 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-11.r27.tokyjp05.jp.bb.gin.ntt.net (129.250.2.154) 4.03 ms AS2914 Japan Tokyo Tokyo ntt.com
8 *
9 *
10 202.97.34.157 109.75 ms AS4134 China Beijing Telecom
11 *
12 *
13 6.254.120.106.static.bjtelecom.net (106.120.254.6) 107.99 ms AS4847 China Beijing Telecom
14 142.243.120.106.static.bjtelecom.net (106.120.243.142) 107.59 ms AS4847 China Beijing Telecom
===== Return [Beijing Telecom] route test completed =====
===== Testing [Beijing Unicom] return route =====
traceroute to 103.254.70.52 (103.254.70.52), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 43.39 ms AS20473 Japan Tokyo Tokyo choopa.com
3 *
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 1.61 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.6.188) 1.92 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-4.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.3.57) 2.02 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-10.r26.tokyjp05.jp.bb.gin.ntt.net (129.250.2.152) 1.71 ms AS2914 Japan Tokyo Tokyo ntt.com
8 202.97.94.9 82.06 ms AS4134 China Shanghai Telecom
9 202.97.90.30 86.60 ms AS4134 China Shanghai Telecom
10 202.97.94.238 88.84 ms AS4134 China Shanghai Telecom
11 202.97.34.149 107.28 ms AS4134 China Beijing Telecom
12 *
13 *
14 *
15 119.40.40.74 132.06 ms AS4847 China Beijing cnispunion.org Unicom
16 *
17 103.254.70.52 112.12 ms AS4808,AS4847 China Beijing Unicom/Telecom
===== Return [Beijing Unicom] route test completed =====
===== Testing [Beijing Mobile] return route =====
traceroute to 218.205.152.14 (218.205.152.14), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 16.58 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 1.02 ms AS20473 Japan Tokyo Tokyo choopa.com
4 *
5 ce-0-14-0-1.r02.tokyjp05.jp.bb.gin.ntt.net (120.88.54.97) 2.43 ms AS2914 Japan Tokyo Tokyo ntt.com
6 *
7 ae-4.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 50.50 ms AS2914 China Hong Kong ntt.com
8 ae-1.r03.tkokhk01.hk.bb.gin.ntt.net (129.250.6.98) 50.19 ms AS2914 China Hong Kong ntt.com
9 ae-1.a01.chwahk02.hk.bb.gin.ntt.net (129.250.5.161) 51.50 ms AS2914 China Hong Kong ntt.com
10 203.131.254.2 49.16 ms AS2914 China Hong Kong ntt.com
11 *
12 223.120.2.2 54.42 ms AS58453 China Guangdong Guangzhou Mobile
13 223.120.22.21 87.17 ms AS58453 China Guangdong Guangzhou Mobile
14 221.183.55.102 298.44 ms AS9808 China Beijing Mobile
15 221.183.46.254 87.28 ms AS9808 China Beijing Mobile
16 221.176.27.253 152.95 ms AS9808 China Beijing Mobile
17 *
18 *
19 211.136.63.106 88.03 ms AS56048 China Beijing Mobile
20 218.205.152.14 89.40 ms AS56048 China Beijing Mobile
===== Return [Beijing Mobile] route test completed =====
===== Testing [Shanghai Mobile] return route =====
traceroute to 117.131.14.202 (117.131.14.202), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 12.84 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 1.05 ms AS20473 Japan Tokyo Tokyo choopa.com
4 *
5 ce-0-14-0-1.r02.tokyjp05.jp.bb.gin.ntt.net (120.88.54.97) 2.64 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-3.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.23) 2.20 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-4.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 50.40 ms AS2914 China Hong Kong ntt.com
8 ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92) 54.46 ms AS2914 China Hong Kong ntt.com
9 ae-2.a01.chwahk02.hk.bb.gin.ntt.net (129.250.6.123) 59.84 ms AS2914 China Hong Kong ntt.com
10 203.131.254.2 49.43 ms AS2914 China Hong Kong ntt.com
11 223.120.2.53 49.60 ms AS58453 China Hong Kong Mobile
12 223.120.2.2 54.56 ms AS58453 China Guangdong Guangzhou Mobile
13 223.120.22.5 78.88 ms AS58453 China Shanghai Mobile
14 221.183.55.26 80.49 ms AS9808 China Shanghai Mobile
15 221.176.22.205 79.56 ms AS9808 China Shanghai Mobile
16 221.176.22.13 80.06 ms AS9808 China Shanghai Mobile
17 221.176.19.58 78.65 ms AS9808 China Shanghai Mobile
18 221.181.125.154 80.03 ms AS24400 China Shanghai Mobile
19 117.131.14.202 81.55 ms AS24400 China Shanghai Mobile
===== Return [Shanghai Mobile] route test completed =====
===== Testing [Shanghai Telecom] return route =====
traceroute to 211.144.205.58 (211.144.205.58), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 16.58 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 2.57 ms AS20473 Japan Tokyo Tokyo choopa.com
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 62.10 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-25.r02.tokyjp05.jp.bb.gin.ntt.net (129.250.6.182) 2.19 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-3.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.23) 2.04 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-9.r24.osakjp02.jp.bb.gin.ntt.net (129.250.7.79) 9.18 ms AS2914 Japan Osaka Osaka ntt.com
8 ae-20.r00.osakjp02.jp.bb.gin.ntt.net (129.250.5.39) 9.53 ms AS2914 Japan Osaka Osaka ntt.com
9 219.158.39.197 116.61 ms AS4837 China Shanghai Unicom
10 219.158.113.126 125.50 ms AS4837 China Shanghai Unicom
11 219.158.113.113 110.49 ms AS4837 China Shanghai Unicom
12 *
13 112.64.252.86 120.11 ms AS17621 China Shanghai Unicom
14 140.207.48.250 117.57 ms AS17621 China Shanghai Unicom
15 208.162.dsnet (211.144.208.162) 108.13 ms AS23853 China Shanghai shuxun.net Telecom/Unicom
16 208.134.dsnet (211.144.208.134) 118.50 ms AS23853 China Shanghai shuxun.net Telecom/Unicom
17 205.58.dsnet (211.144.205.58) 108.55 ms AS17621,AS23853 China Shanghai shuxun.net Telecom/Unicom
===== Return [Shanghai Telecom] route test completed =====
===== Testing [Shanghai Unicom] return route =====
traceroute to 220.196.42.133 (220.196.42.133), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 20.79 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 1.23 ms AS20473 Japan Tokyo Tokyo choopa.com
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 15.15 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.6.188) 1.82 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-4.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.34) 2.02 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-9.r24.osakjp02.jp.bb.gin.ntt.net (129.250.7.79) 9.45 ms AS2914 Japan Osaka Osaka ntt.com
8 ae-20.r00.osakjp02.jp.bb.gin.ntt.net (129.250.5.39) 9.42 ms AS2914 Japan Osaka Osaka ntt.com
9 *
10 219.158.113.126 113.83 ms AS4837 China Shanghai Unicom
11 *
12 *
13 112.64.247.194 112.50 ms AS17621 China Shanghai Unicom
14 112.65.207.162 102.99 ms AS17621 China Shanghai Unicom
15 140.207.207.37 101.11 ms AS17621 China Shanghai Unicom
16 140.207.207.186 114.45 ms AS17621 China Shanghai Unicom
17 220.196.42.133 102.02 ms AS17621 China Shanghai Unicom
===== Return [Shanghai Unicom] route test completed =====
===== Testing [Guangdong Unicom] return route =====
traceroute to 27.40.0.30 (27.40.0.30), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 16.63 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 2.04 ms AS20473 Japan Tokyo Tokyo choopa.com
4 ae-12.r01.tokyjp05.jp.bb.gin.ntt.net (120.88.53.65) 22.58 ms AS2914 Japan Tokyo Tokyo ntt.com
5 ae-4.r03.tokyjp05.jp.bb.gin.ntt.net (129.250.6.188) 2.37 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-4.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.34) 2.19 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-9.r26.tokyjp05.jp.bb.gin.ntt.net (129.250.2.10) 1.79 ms AS2914 Japan Tokyo Tokyo ntt.com
8 219.158.42.5 63.99 ms AS4837 China Guangdong Guangzhou Unicom
9 219.158.98.93 67.69 ms AS4837 China Guangdong Guangzhou Unicom
10 219.158.24.125 59.30 ms AS4837 China Guangdong Guangzhou Unicom
11 120.81.0.34 60.63 ms AS17816 China Guangdong Guangzhou Unicom
12 221.4.6.2 61.73 ms AS17816 China Guangdong Guangzhou Unicom
13 27.40.0.30 60.70 ms AS17816 China Guangdong Guangzhou Unicom
===== Return [Guangdong Unicom] route test completed =====
===== Testing [Guangdong Mobile] return route =====
traceroute to 211.139.129.222 (211.139.129.222), 30 hops max, 60 byte packets
1 *
2 209.222.31.33 17.33 ms AS20473 Japan Tokyo Tokyo choopa.com
3 vl627-br2-cer.tyo1.choopa.net (45.76.201.93) 1.02 ms AS20473 Japan Tokyo Tokyo choopa.com
4 *
5 ce-0-14-0-1.r02.tokyjp05.jp.bb.gin.ntt.net (120.88.54.97) 2.44 ms AS2914 Japan Tokyo Tokyo ntt.com
6 ae-3.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.3.23) 3.10 ms AS2914 Japan Tokyo Tokyo ntt.com
7 ae-4.r24.tokhk01.hk.bb.gin.ntt.net (129.250.2.51) 50.28 ms AS2914 China Hong Kong ntt.com
8 ae-1.r02.tokhk01.hk.bb.gin.ntt.net (129.250.6.92) 54.53 ms AS2914 China Hong Kong ntt.com
9 ce-0-4-0-0.r02.tokhk01.hk.ce.gin.ntt.net (203.131.241.82) 47.76 ms AS2914 China Hong Kong ntt.com
10 223.120.2.117 47.23 ms AS58453 China Hong Kong Mobile
11 223.120.2.82 53.15 ms AS58453 China Hong Kong Mobile
12 221.183.55.82 54.49 ms AS9808 China Guangdong Guangzhou Mobile
13 221.183.25.118 53.30 ms AS9808 China Guangdong Guangzhou Mobile
14 221.176.22.157 57.43 ms AS9808 China Guangdong Guangzhou Mobile
15 221.183.14.126 56.49 ms AS9808 China Guangdong Guangzhou Mobile
16 120.198.206.198 59.19 ms AS56040 China Guangdong Guangzhou Mobile
17 120.197.27.250 59.96 ms AS56040 China Guangdong Guangzhou Mobile
18 211.139.129.222 57.43 ms AS56040 China Guangdong Guangzhou Mobile
===== Return [Guangdong Mobile] route test completed =====
----------------------------------------------------------------------
【Sichuan Telecom】 - 125.64.38.178
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 128.773/128.972/129.617/0.253 ms
----------------------------------------------------------------------
【Beijing Telecom】 - 106.120.243.142
10 packets transmitted, 10 received, 0% packet loss, time 9006ms
rtt min/avg/max/mdev = 107.442/107.535/107.645/0.394 ms
----------------------------------------------------------------------
【Beijing Unicom】 - 103.254.70.52
10 packets transmitted, 9 received, 10% packet loss, time 9013ms
rtt min/avg/max/mdev = 109.617/109.884/110.060/0.305 ms
----------------------------------------------------------------------
【Beijing Mobile】 - 218.205.152.14
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 89.018/89.152/89.315/0.210 ms
----------------------------------------------------------------------
【Shanghai Mobile】 - 117.131.14.202
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 80.851/81.351/81.915/0.435 ms
----------------------------------------------------------------------
【Shanghai Telecom】 - 211.144.205.58
10 packets transmitted, 4 received, 60% packet loss, time 9125ms
rtt min/avg/max/mdev = 108.511/109.197/110.554/0.875 ms
----------------------------------------------------------------------
【Shanghai Unicom】 - 220.196.42.133
10 packets transmitted, 9 received, 10% packet loss, time 9020ms
rtt min/avg/max/mdev = 101.208/101.942/102.581/0.503 ms
----------------------------------------------------------------------
【Guangdong Unicom】 - 27.40.0.30
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 60.410/61.356/62.579/0.582 ms
----------------------------------------------------------------------
【Guangdong Mobile】 - 211.139.129.222
10 packets transmitted, 10 received, 0% packet loss, time 9015ms
rtt min/avg/max/mdev = 56.736/57.183/57.598/0.407 ms
----------------------------------------------------------------------
min: minimum latency
avg: average latency
max: maximum latency
mdev: average deviation
----------------------------------------------------------------------
Script Source: https://www.94ish.me/1752.html