Simple evaluation of henghost Japanese cloud server, China Telecom + China Unicom via CN2, China Mobile NTT direct connection

Hong Kong Hengchuang Technology (henghost) recently launched a new Japanese cloud server (Japanese vps) in the Japanese computer room. According to the official statement: the cluster is deployed in the Equinix TY8 IBX™ data center in Tokyo, and KDDI+SoftBank+IIJ+NTT builds a comprehensive Penetrating the dynamic BGP network, Japan CN2 GIA (AS4809) returns to China at high speed. Let’s eat some crabs here first and explore the path for everyone. The data is for reference only!

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

The tested cloud server configuration is 4G memory, 2 cores, 60G hard disk, and 10M bandwidth. According to the cloud server obtained, the CPU is e5-2697v3 (2.6GHz frequency). The webmaster easily enabled BBR and the hard disk. I/O is roughly 220MB/S:

The data for FIO test hard disk read and write are as follows:

During the day, let’s test the uplink and downlink bandwidth of speedtest.net’s three network nodes in mainland China. From the data point of view, the uplink we need most is basically close to full, but the downlink bandwidth is somewhat insufficient. Satisfying:

Comparing it again during the evening peak period, there is still little change, or even no change:

Try other nodes in Asia:

iperf3 running in Europe and the United States:

For files stored on the test VPS, the download speed was tested during the day. The webmaster is Guangzhou Telecom, and the download speed is as follows:

During the evening peak period, compared with the daytime, there is attenuation, but it is still acceptable:

Those who are concerned about latency can take a look. The data is tested by more than 60 nodes on ping.chinaz.com:

For the outbound journey of China Telecom, take CN2:

China Unicom’s outbound journey, China Unicom’s backbone connects NTT directly to Japan’s computer room:

Mobile outbound journey, Hong Kong CMI picks up NTT to Japan:

Return to Mainland China Telecom: CN2 direct return to China

Return to China Unicom: CN2 link and then transfer to China Unicom

Return to China Mobile: Take NTT to Hong Kong and transfer to the Hong Kong mobile node for direct connection back to China

Test streaming media unlocking, for reference only:

Unix bench Mark：

To summarize:

Telecom, two-way CN2, nothing to say, it’s awesome;

China Unicom: For the outbound journey, the backbone connects to NTT, which is not bad; for the return journey, it switches to Telecom CN2 and then to China Unicom, which is well optimized;

Mobile: The outbound CMI in Hong Kong connects to NTT, and the return NTT goes to Hong Kong and then transfers to the Hong Kong node to directly connect to the mainland. Optimization is in place.

In general, the speed is not bad, and it can be used for remote office, website building, etc.!

Evaluation of Hengchuang Cloud Server:

Hong Kong Cloud: https:// /45516.html

Japan Cloud: https:// /48326.html

American Cloud: https:// /45776.html

Recommended site search: Alibaba Cloud free virtual host, registration network, server hosting, domain name registration query, vps host, vps US server, vps server rental, registration system, php virtual host, foreign server,