How about Linode? [2022] Linode Canadian Data Center Cloud Server Evaluation

What about linode? How about linode Canadian cloud server? Although Canada is right next to the United States, judging from the current market situation, it seems that the network effect in mainland China is almost the same as that in Europe. So is linode's Canadian computer room still suitable for mainland Chinese user groups? How is the network? How is the performance? Let's take everyone to take a look at the test data. What the data says is what it is.

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

It seems that other computer rooms are currently using AMD EPYC 7601, while the Canadian computer room seems to be using 7501. Although the difference is not big, it is still an exception. The current hard disk I/O is approximately 593MB/s, and the webmaster has enabled BBR:

FIO tests the read and write data of the hard disk in detail, and the results are as follows:

We will test how much uplink and downlink bandwidth the chicken can run in broad daylight. The first node is the nearest node, and the rest are the three network nodes in mainland China. The approximate data is as follows:

Comparing the data during the day and the evening peak period, it seems that telecommunications and mobile services are attenuated more? !

The puppies tested by iperf3 on European and American nodes are still very cool:

Guangzhou Telecom directly uses Chrome to download the files stored on the test chicken to test the speed, during the day:

The night is reduced to almost one-tenth of the daytime:

Latency monitoring results of more than 170 nodes around the world:

For the outbound telecommunications journey, the backbone network is connected to NTT. Log in from San Jose on the west coast of the United States and then go to Chicago and then to Toronto, Canada:

China Unicom's outbound journey, China Unicom backbone docking with TATA: log in from Los Angeles on the west coast of the United States, then go to Chicago and then to Toronto, Canada:

For the outbound journey, International CMI takes cogentco from San Jose to Canada via the United States in a large circle:

Return to China Telecom:

Beijing direction: Canada takes TATA to Telecom’s San Jose node, and then directly connects back;

Shanghai direction: Canada takes Telia to Telecom New York node, and then directly connects back;

Guangzhou direction: Canada takes NTT Telecom’s Los Angeles node, and then connects directly back

Return to China Unicom:

Beijing direction: Canada takes telia to the United Kingdom, France, and Germany, and then takes AS4837 back;

Shanghai direction: From Canada, take telia to the San Jose node of America Unicom, and then as4838 back;

Guangzhou direction: Take TATA from Canada to San Jose, USA, and then AS483 back,

Return, move to mainland China:

Beijing direction: Canada takes Telia to Mobile America’s San Jose node, and then directly connects back

Shanghai direction: Canada takes NTT to Seattle in the United States, then to Tokyo, Japan, then to Hong Kong, and then back directly

Guangzhou direction: Take Telia from Canada to the Seattle node of Mobile America, and then directly connect back

Streaming media detection:

TIKTOK seems to be on hiatus:

Unix bench Mark：

To summarize:

On the outbound journey, all three networks have no distinctive features;

The return journey, from the perspective of line optimization, is roughly China Mobile>China Unicom>Telecom;

The performance is average, and there is not much advantage. Whether you go or come back, you have to pass through the West Coast of the United States, which is not very interesting.

Recommended site searches: cloud server rental platform, proxy filing, asp website space, anti-complaint vps host, registered domain name query, proxy ip, telecom host rental, dynamic vps second ip change, foreign vps server rental, space rental, < /p>