Simple test of DogYun Korean data center elastic cloud server

The blog has shared DogYun product information several times. Regarding the question of how good DogYun is, we have also tested Hong Kong KC, Hong Kong BGP, Germany CUVIP and other data center products. Today, let's take a look at the Korean host. This test is a dynamic cloud server in the Korean data center. The minimum configuration is preferred, and it is not a new node for the merchant. The simple test results are posted below for your reference.

Official website: www.dogyun.com

Host Configuration

I'm used to this test, so I definitely use the lowest configuration. This time I used the lowest single-core CPU + 2GB memory + 20G hard disk package of the Korean Dynamic Cloud Server, and installed the operating system CentOS7.*

Basic Information

The VPS hosts provided by DogYun are managed directly in the member center, with comprehensive functions, including the basic management functions we commonly use (power on and off, restart, reinstall the system, etc.), as well as resource and traffic monitoring and self-service transfer products.

IO/Bandwidth Test

The IO and bandwidth tests also use the one-click package. Based on the principle of fair use, the merchant has limited the IO. The bandwidth of this package is 50Mbps.

It can be seen above that the bandwidth is completely consistent with the package and is provided in full. The IO is the limited value. Below is another one-click package test information.

Outbound Routing

First of all, for telecommunications, the backbone personnel went directly to South Korea and transferred to the computer room.

Move CMI to Korea.

China Unicom uses AS4837 to reach South Korea, and the three networks are basically the same, with no detours.

Backhaul Routing

 Beijing Telecom traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets
 1 45.154.13.1 0.63 ms AS138195 South Korea, Seoul, rhinocloud.uk
 4 59.43.187.209 42.95 ms * China, Shanghai, chinatelecom.com.cn, Telecom5 59.43.182.225 60.15 ms * China, Beijing, chinatelecom.com.cn, Telecom6 59.43.246.142 48.58 ms * China, Beijing, chinatelecom.com.cn, Telecom7 202.97.85.61 50.71 ms AS4134 China, Beijing, chinatelecom.com.cn, Telecom8 *
 9 *
10 2.254.120.106.static.bjtelecom.net (106.120.254.2) 69.02 ms AS4847 China, Beijing, chinatelecom.com.cn, Telecom 11 bj141-147-210.bjtelecom.net (219.141.147.210) 63.70 ms AS4847 China, Beijing, chinatelecom.com.cn, Telecom ------------------------------------------------------------------
Shanghai Telecom traceroute to 202.96.209.133 (202.96.209.133), 30 hops max, 32 byte packets
 1 45.154.13.1 0.74 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 1.85 ms * LAN3 203.195.115.25 43.35 ms AS4809 Korea, Seoul, chinatelecom.com.cn, Telecom4 59.43.250.33 43.87 ms * China, Shanghai, chinatelecom.com.cn, Telecom5 *
 6 202.97.51.162 50.33 ms AS4134 China, Shanghai, chinatelecom.com.cn, Telecom7 202.97.24.145 61.95 ms AS4134 China, Shanghai, chinatelecom.com.cn, Telecom8 101.95.120.85 62.61 ms AS4812 China, Shanghai, chinatelecom.com.cn, Telecom9 *
10 124.74.229.230 63.24 ms AS4812 China, Shanghai, chinatelecom.com.cn, Telecom 11 ns-pd.online.sh.cn (202.96.209.133) 62.10 ms AS4812 China, Shanghai, chinatelecom.com.cn, Telecom ------------------------------------------------------------------
Shenzhen Telecom traceroute to 58.60.188.222 (58.60.188.222), 30 hops max, 32 byte packets
 1 45.154.13.1 0.65 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 0.76 ms * LAN3 203.195.115.25 44.79 ms AS4809 South Korea, Seoul, chinatelecom.com.cn, Telecom4 59.43.187.209 42.71 ms * China, Shanghai, chinatelecom.com.cn, Telecom5 59.43.182.238 48.48 ms * China, Guangdong, Guangzhou, chinatelecom.com.cn, Telecom6 59.43.245.30 66.86 ms * China, chinatelecom.com.cn, Telecom7 202.97.94.89 68.26 ms AS4134 China, Guangdong, Guangzhou, chinatelecom.com.cn, Telecom8 *
 9 14.147.127.30 73.48 ms AS134774 China, Guangdong, Shenzhen, chinatelecom.com.cn, Telecom10 *
11 58.60.188.222 75.84 ms AS4134 China, Guangdong, Shenzhen, chinatelecom.com.cn, Telecom----------------------------------------------------------------------
Beijing Unicom traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets
 1 45.154.13.1 0.60 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 1.98 ms * LAN3 211.53.96.21 1.57 ms AS3786 Korea, Seoul, uplus.co.kr
 4 1.208.164.29 1.97 ms AS3786 South Korea, Seoul, uplus.co.kr
 5 1.208.114.94 2.42 ms AS3786 South Korea, Seoul, uplus.co.kr
 6 219.158.43.233 47.71 ms AS4837 China, Beijing, chinaunicom.com, China Unicom7 219.158.3.114 46.85 ms AS4837 China, Beijing, chinaunicom.com, China Unicom8 219.158.3.133 52.96 ms AS4837 China, Beijing, chinaunicom.com, China Unicom9 *
10 125.33.186.250 48.45 ms AS4808 China, Beijing, chinaunicom.com, China Unicom11 202.106.50.1 46.66 ms AS4808 China, Beijing, chinaunicom.com, China Unicom----------------------------------------------------------------------
Shanghai Unicom traceroute to 210.22.97.1 (210.22.97.1), 30 hops max, 32 byte packets
 1 45.154.13.1 0.77 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 0.82 ms * LAN3 211.53.96.21 1.56 ms AS3786 Korea, Seoul, uplus.co.kr
 4 1.208.174.125 2.14 ms AS3786 South Korea, Seoul, uplus.co.kr
 5 1.208.179.54 3.39 ms AS3786 South Korea, Seoul, uplus.co.kr
 6 219.158.33.93 27.19 ms AS4837 China, Shanghai, chinaunicom.com, China Unicom7 219.158.113.142 31.06 ms AS4837 China, Shanghai, chinaunicom.com, China Unicom8 219.158.113.101 24.16 ms AS4837 China, Shanghai, chinaunicom.com, China Unicom9 139.226.225.134 24.54 ms AS17621 China, Shanghai, chinaunicom.com, China Unicom10 139.226.201.146 24.49 ms AS17621 China, Shanghai, chinaunicom.com, China Unicom11 210.22.97.1 26.20 ms AS17621 China, Shanghai, chinaunicom.com, China Unicom----------------------------------------------------------------------
Shenzhen Unicom traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets
 1 45.154.13.1 0.64 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 0.65 ms * LAN3 211.53.96.21 1.53 ms AS3786 Korea, Seoul, uplus.co.kr
 4 1.208.174.125 2.18 ms AS3786 South Korea, Seoul, uplus.co.kr
 5 1.208.179.54 1.77 ms AS3786 South Korea, Seoul, uplus.co.kr
 6 219.158.33.93 26.54 ms AS4837 China, chinaunicom.com, China Unicom7 219.158.113.138 26.72 ms AS4837 China, Shanghai, chinaunicom.com, China Unicom8 *
 88.92 ms AS17623 China, Guangdong, Shenzhen, chinaunicom.com, China Unicom12 dns2-ftcg.gdsz.cncnet.net (210.21.196.6) 84.68 ms AS17623 China, Guangdong, Shenzhen, chinaunicom.com, China Unicom13 219.158.100.202 49.31 ms AS4837 China, Guangdong, Guangzhou, chinaunicom.com, China Unicom14 120.82.0.166 57.39 ms AS17816 China, Guangdong, Shenzhen, chinaunicom.com, China Unicom15 120.80.144.34 88.92 ms AS17623 China, Guangdong, Shenzhen, chinaunicom.com, China Unicom16 dns2-ftcg.gdsz.cncnet.net (210.21.196.6) 84.68 ms AS17623 China, Guangdong, Shenzhen, chinaunicom.com, China Unicom----------------------------------------------------------------------
Beijing Mobile traceroute to 221.179.155.161 (221.179.155.161), 30 hops max, 32 byte packets
 1 45.154.13.1 0.65 ms AS138195 South Korea, Seoul, rhinocloud.uk
 223.120.22.33 48.11 ms AS58453 China, Beijing, chinamobile.com, Mobile7 221.183.55.110 47.94 ms AS58458 China, Beijing, chinamobile.com, Mobile8 223.120.2.90 26.20 ms AS58453 China, Shanghai, chinamobile.com, Mobile9 223.120.22.33 48.11 ms AS58453 China, Beijing, chinamobile.com, Mobile10 221.183.55.110 47.94 ms AS9808 China, Beijing, chinamobile.com, Mobile11 223.120.2.90 26.20 ms AS58453 China, Shanghai, chinamobile.com, Mobile12 223.120.2.33 48.11 ms AS58453 China, Beijing, chinamobile.com, Mobile13 221.183.52.2 51.47 ms AS9808 China, Beijing, chinamobile.com, Mobile 9 221.183.89.122 49.30 ms AS9808 China, Beijing, chinamobile.com, Mobile 10 221.183.46.178 50.53 ms AS9808 China, Beijing, chinamobile.com, Mobile 11 *
12 cachedns03.bj.chinamobile.com (221.179.155.161) 51.91 ms AS56048 China, Beijing, chinamobile.com, Mobile----------------------------------------------------------------------
Shanghai Mobile traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets
 1 45.154.13.1 0.63 ms AS138195 South Korea, Seoul, rhinocloud.uk
 223.176.22.205 2.84 ms AS58453 China, Shanghai, chinamobile.com, Mobile 8 223.176.22.206 2.84 ms AS58453 China, Shanghai, chinamobile.com, Mobile 9 223.176.22.206 2.84 ms AS58453 China, Shanghai, chinamobile.com, Mobile 10 223.176.22.206 2.84 ms AS58453 China, Shanghai, chinamobile.com, Mobile 11 223.176.22.206 2.84 ms AS58453 China, Shanghai, chinamobile.com, Mobile 221.176.22.33 27.37 ms AS9808 China, Shanghai, chinamobile.com, Mobile9 111.24.4.77 27.58 ms AS9808 China, Shanghai, chinamobile.com, Mobile10 111.24.4.106 27.60 ms AS9808 China, Shanghai, chinamobile.com, Mobile11 221.181.125.113 27.95 ms AS24400 China, Shanghai, chinamobile.com, Mobile12 211.136.190.234 27.67 ms AS24400 China, Shanghai, chinamobile.com, Mobile13 211.136.112.252 28.17 ms AS24400 China, Shanghai, chinamobile.com, Mobile 14 211.136.112.200 28.35 ms AS24400 China, Shanghai, chinamobile.com, Mobile----------------------------------------------------------------------
Shenzhen Mobile traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets
 1 45.154.13.1 0.62 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 0.86 ms * LAN3 223.119.21.13 2.27 ms AS58453 South Korea, Seoul, chinamobile.com, Mobile4 223.120.3.113 2.14 ms AS58453 South Korea, Seoul, chinamobile.com, Mobile5 223.120.3.221 37.69 ms AS58453 China, Hong Kong, chinamobile.com, Mobile6 223.120.2.10 48.66 ms AS58453 China, Guangdong, Guangzhou, chinamobile.com, Mobile7 221.183.55.58 48.39 ms AS9808 China, Guangdong, Guangzhou, chinamobile.com, Mobile 8 221.183.52.85 48.18 ms AS9808 China, Guangdong, Guangzhou, chinamobile.com, Mobile9 221.176.18.109 48.14 ms AS9808 China, Guangdong, Guangzhou, chinamobile.com, Mobile10 111.24.4.245 48.37 ms AS9808 China, Guangdong, Guangzhou, chinamobile.com, Mobile11 221.183.71.70 50.67 ms AS9808 China, Guangdong, chinamobile.com, Mobile12 221.183.110.166 52.81 ms AS9808 China, chinamobile.com, Mobile13 ns6.gd.cnmobile.net (120.196.165.24) 50.56 ms AS56040 China, Guangdong, Shenzhen, chinamobile.com, Mobile----------------------------------------------------------------------
Chengdu Education Network traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 32 byte packets
 1 45.154.13.1 0.70 ms AS138195 South Korea, Seoul, rhinocloud.uk
 2 10.200.0.25 0.81 ms * LAN3 203.195.115.25 43.45 ms AS4809 South Korea, Seoul, chinatelecom.com.cn, Telecom4 59.43.250.33 45.52 ms * China, Shanghai, chinatelecom.com.cn, Telecom8 202.97.29.158 68.39 ms AS4134 China, Hubei, Wuhan, chinatelecom.com.cn, Telecom9 *
10 101.4.116.158 86.31 ms AS4538 China, Sichuan, Chengdu, edu.cn, education network18 202.112.14.151 84.49 ms AS24355 China, Sichuan, Chengdu, edu.cn, education network

Latency Test

The latency was tested by pinging 370 nodes in China and Asia.

In general, the latency is slightly higher than the direct connection to Hong Kong, but compared to the overwhelming level of Europe and the United States, the low latency plus sufficient bandwidth makes remote use very smooth. Those who are interested can pay attention to it. In addition to dynamic cloud servers, the merchant also provides classic cloud servers in the Korean data center.