henghost: A simple evaluation of Hong Kong CN2 GIA line VPS, the actual test data tells you how henghost is like

henghost (Hengchuang Technology) operates cloud servers and independent server services in Hong Kong, South Korea, Japan, and the United States. It is connected to the CN2+BGP network and has additional high-defense services. How about henghost? How about Hengchuang Technology? We have no way to answer, so let’s go straight to the machine, write a review, and use data to tell everyone how henghost is! Note: The data is for reference only.

Official website: https://www.henghost.com

Promotion in August: https:// /45428.html

The cloud server I got has an e5-2680v3 CPU, 1G memory, 1 core, 50G cloud disk, 10Mbps bandwidth, the webmaster has enabled BBR, and the hard disk I/O is roughly around 111MB/S:

FIO test:

During leisure time during the day, speedtest.net China node tests the uplink bandwidth and downlink bandwidth of the cloud server. The uplink is limited to 10Mbps, and the downlink seems to be 50Mbps:

Tested at 7:58 during the evening peak, the uplink and downlink bandwidths are basically the same, unlike in Europe and America where they almost explode at night:

The test results of other nodes in Asia are as follows:

iperf3 European and American test results are as follows:

Guangzhou Telecom, directly download the files on the VPS during the day to measure the speed, 1113KB/S,

At 10:05 in the evening rush hour, the download speed is 1106KB/S, which is almost the same as during the day:

The ping data tested on 80 nodes in mainland China is as follows, the picture is provided by ping.chinaz.com:

A piece of green, the effect still looks very comfortable:

For the outgoing China Telecom service, take CN2:

China Unicom’s outbound journey also takes CN2:

Moving, the outgoing journey is really unchangeable:

For the return trip to China Telecom: take CN2

Return to China Unicom: AS4837 back to mainland China

Return, move to the mainland: direct connection back to the mainland

To summarize: for the outbound journey, China Telecom and China Unicom use CN2, and China Mobile uses their own CMI; for the return journey, China Telecom uses CN2, China Unicom uses AS4837, and China Mobile uses direct connection. In other words, this is still carefully optimized, but it may be better if there is a little more cost to force this mobile phone to use China Telecom CN2. China Unicom AS4837 is not a big problem and can be done.

Finally, post a Unix bench, it looks ok:

Recommended site search: virtual host, registered domain name, Korean server rental, Henan virtual host, Zhenjiang high-defense server, game server rental, domain name reservation, virtual host Hong Kong host, ip proxy server, rent server,