How about raksmart Japanese bare metal cloud? Sharing actual measured data to tell you the details

raksmart computer room not only has independent server business, cloud server (and VPS), but also a kind of business between cloud-based and independent called "bare metal cloud", which is a bit similar, just like "bare metal server". Of course, raksmart's bare metal cloud has been deployed in data centers in the United States, Japan, and Hong Kong (click here to view reviews). What we bring to you today is the actual measured data sharing of Japanese computer rooms, for reference only!

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

U.S. company, no real name required, bilingual in Chinese and English, payment via PayPal, Alipay, WeChat, credit card, Bitcoin, etc.

Bare metal servers are 30% off, discount code: Bare-Metal Cloud-30%dis

Value-added items: Mainland optimized bandwidth can be expanded to 1Gbps, premium network (via CN2) can be expanded to 200Mbps, IP maximum 64, memory maximum 256G, data disk maximum 10T SSD

The CPU of the test machine I got is e5-2697v2, and the hard disk I/O is about 366MB/S. I turned on BBR and noticed that the system is actually KVM virtual:

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

The official default bandwidth is 50Mbps (mainland optimized series). I would like to know how much peak value can be reached in the three-network environment of mainland China? Use speedtest.net to test it on the three network nodes in mainland China:

Comparing the effect of the evening rush hour, it is basically full:

The effect of running other nodes in the Asian region is also close to full:

The general status of iperf3 running in Europe and the United States:

The webmaster of the files stored on the test machine is Guangzhou Telecom. The download speed directly using Chrome is as follows:

The test effect of the evening peak when the backbone network explodes is like this. Basically, attenuation is not a problem:

If you are concerned about the delay issue, you can look at the monitoring values ​​of more than 60 nodes in mainland China:

Telecom’s outbound route is SoftBank:

China Unicom’s outbound journey is directly connected to SoftBank’s bgp.net network:

For the outbound journey, take the CMI, then the Softbank line, and then the bgp.net network to the computer room:

Return to China Telecom: Directly connect to China Unicom AS4837 and then transfer to China Telecom

For the return trip to China Unicom: take Telecom CN2 and transfer to China Unicom after returning to China

Return to mobile in mainland China: The Japanese computer room takes NTT directly to Hong Kong, and then transfers to the mobile Hong Kong node and comes back directly

Unix bench

Streaming media detection, for reference only:

To summarize:

Advantages: The outbound journey is straightened, basically taking the Japanese Softbank route; the return journey, via CN2, China Unicom AS4837, China Mobile is also directly connected; that is to say, the network is quite reliable;

Disadvantages: This is a "bare metal cloud", which is virtualized by KVM. There is a big gap in performance with independent servers, and it is not suitable for running businesses with high CPU requirements. The webmaster understands that this roughly falls within the scope of business between VPS and independent servers.

I found a big problem: China Telecom uses China Unicom AS4837, and China Unicom uses China Telecom CN2. It is probably the wrong adjustment. I hope it will be changed back soon to be more reliable!

Recommended site searches: virtual host purchase, vps virtual server Hong Kong cloud host, domain name service provider, domain name registration query, registered cn domain name, website IP address query, online filing query, Korean agent ip, cm domain name,