Which computer room does Google Cloud audition? GCP China Taiwan/Hong Kong/Singapore/Japan Node Network Delay Competition
Small partners who do foreign trade, cross-border e-commerce, sea games, or self-built nodes often have difficulty choosing Google Cloud (GCP) Asian computer rooms.
Google Cloud has four core computer rooms in Asia Pacific:
Taiwan (asia-east1), Hong Kong (asia-east2), Singapore (asia-southeast1) and Tokyo (asia-northeast1)
. Many people's misconception is that "I will choose whoever is close to me". As a result, they spent a lot of money to buy servers in Hong Kong or Taiwan, only to find that overseas users visit cards like PPT. Or for the sake of cheap choice, the domestic visit delay is so high that life is doubtful.
Don't look at the official network topology map on those tall. This tutorial we do not carry official empty words, directly from
Physical distance, domestic direct connection, overseas (Southeast Asia/Europe and the United States) radiation capacity, computer room bandwidth cost
The four dimensions will help you to completely clean up these four Asia Pacific nodes.
1. the bottom core: why Google cloud network is different from others?
Before the competition is delayed, you must understand a Google cloud exclusive killer:
Google Global Backbone Network (Premium Tier)
.
For the sea-going computer rooms of many domestic cloud manufacturers (such as Aliyun and Tengxun Cloud International Station), when the public network traffic leaves the computer room, they have to squeeze together with ordinary netizens in the sea of the public network until they swim to the country where the users are located.
But Google Cloud uses the default
Premium Network Layer (Premium Tier)
:
As long as your users make a request to your server locally, the traffic will immediately jump into Google's self-built global fiber backbone network. For the next few thousand kilometers, the data is all speeding along Google's private top highways until it enters your target instance.
This determines:
GCP's cross-country latency is much more stable than the normal public network.
Full Analysis of Network Delay and Location of Four Asian Nodes in 2.
We will give these four nodes a big competition based on the visits to the domestic base camp and overseas core markets.
1. China Hong Kong node (asia-east2) -domestic users of the "white moonlight", overseas "outsiders"
Hong Kong computer room is the GCP node closest to mainland China and the first choice for countless people.
Domestic delay: very low. The ping value in South China (Shenzhen/Guangzhou) is usually between 10ms-20ms, and that in East China/North China is also around 40ms-60ms.
Sea radiation capacity: embarrassment. The delay for Hong Kong nodes to travel to Southeast Asia (such as Indonesia and Thailand) is 60ms-90ms. Going to Europe and the United States is basically around half of the world, with a delay of 150ms.
Fatal pain point: extremely dependent on the three major domestic operators of cross-border export cable. Once it reaches the evening peak (18:00 - 23:00), the domestic export backbone network is blocked, and even if the Hong Kong node is closer to you, packet loss, disconnection and delay will soar.
(because the mainland public network that has not been optimized is stuck when leaving the country).
Application scenario: purely to provide domestic users with high-quality access (and inconvenient for filing), or mainly to do business projects for Hong Kong, Macao and Taiwan in China.
2. China Taiwan node (asia-east1) -seriously underestimated "cost-effective magic machine"
Taiwan's Changhua computer room is one of Google's earliest and largest data centers in Asia.
Domestic delay: OUTPERFORM. Although it is separated by a strait, because Fujian, Shanghai and other places have direct submarine cables to Taiwan, the delay between East China and South China directly to Taiwan can even reach 30ms-50ms. The tolerance of the late peak is even slightly better than that of Hong Kong at times.
Sea radiation capacity: good. As Google's base camp in Asia, its latency to Japan, South Korea and Hong Kong is extremely low (20ms - 40ms), and its radiation to Southeast Asia is about 60ms.
Core advantage: cheap! The price of computing power (CPU/memory) of Taiwan nodes is usually 10% - 15% cheaper than that of Hong Kong and Singapore, and the quota is very sufficient.
Applicable scenarios: limited budget, taking into account domestic visits, while taking into account Japan and South Korea and Taiwan China's local market to the sea business.
3. Singapore node (asia-southeast1) -the absolute overlord of Southeast Asia
If your target market is Southeast Asia (Indonesia, Vietnam, Thailand, Philippines, Malaysia), close your eyes and choose Singapore.
Overseas delays: Terror low. Singapore is the network hub of the entire Southeast Asia, and the delay of radiation to Singapore, Malaysia, Thailand and Indonesia is basically within 5ms-30ms.
Domestic delays: general. Due to the long geographical distance, the delay of domestic direct connection to Singapore is about 80ms-120ms, which is not suitable for providing high-frequency interaction (such as real-time games) to domestic users.
Core advantage: the crossroads of international submarine cables. Apart from Southeast Asia, Singapore's backbone network delays to India, the Middle East and even Europe are very beautiful.
Applicable scenarios: cross-border e-commerce (Shopee/Lazada shrimp skin construction station), Southeast Asia hand tour, sea pan entertainment APP.
4. Tokyo, Japan (asia-northeast1) -Pan Pacific and Europe and the United States transit station
The Tokyo node is another super port in the Asia-Pacific region.
Domestic delay: drought and flood to protect the harvest. The delay of direct connection to Tokyo in the northern region (Beijing, Shandong and Liaoning) is amazing, which can reach 40ms - 60ms (faster than going to Hong Kong); In the south, it is about 70ms-90ms.
Sea-to-sea radiation capabilities: linking bridgeheads in North America. Tokyo has a large number of trans-Pacific submarine cables directly to the west coast of the United States (Los Angeles/San Jose), and the delay can be controlled at about 100ms - 120ms from Japan to the United States.
Fatal pain point: expensive. Tokyo's computer room resources and electricity costs are extremely high, and the unit price of the machine is among the best in the Asia-Pacific region.
Applicable scenarios: cross-border Japan and South Korea
business, facing North America and taking into account the business of the domestic northern development team.
Horizontal Evaluation Table of Network Delay in Four Major Computer Rooms in 3.
In order to give you a visual comparison, we have made a matrix of the average delay (Latency) to reach these four GCP rooms from each major region:
Target data center \Access source
South China (Shenzhen/Guangzhou)
North China (North/Mountain)
Southeast Asia (Indonesia/Thailand)
Northeast Asia (Japan/Korea)
West Coast of North America (US)
Power cost rating
Hong Kong, China (asia-east2)
10ms - 20ms
50ms - 70ms
60ms - 90ms
50ms - 70ms
160ms +
expensive (★★★★☆)
Taiwan, China (asia-east1)
30ms - 50ms
50ms - 60ms
50ms - 70ms
30ms - 40ms
140ms +
The most cost-effective (★★☆ ☆)
Singapore (asia-southeast1)
80ms - 100ms
100ms - 120ms
5ms - 30ms
70ms - 90ms
180ms +
Standard (★★★☆☆)
Tokyo, Japan (asia-northeast1)
70ms - 90ms
40ms - 60ms
70ms - 90ms
10ms - 20ms
100ms - 120ms
The most expensive (★★★★★)
Note: The above data is based on the Google Premium Tier network. If domestic operators encounter international export failures or late peak QoS speed limits, the delay and packet loss rate of domestic sources will increase.
4. "Copy Job" Selection Guide for Offshore Business
Don't just look at the delay numbers, doing business depends on the line of business. Direct check-in:
1. Cross-border e-commerce TikTok/independent station (Shopify, etc.)
If you do Pan Southeast Asia: choose Singapore (asia-southeast1). Southeast Asian consumers are extremely sensitive to the speed of web page opening, and Singapore nodes can guarantee seconds.
If you do Europe and the United States/Global: Do not choose Asian computer rooms. Direct beauty pageant (us-central1 or us-west1). The US West is the center of the global Internet, and its machines and traffic charges are nearly 30% cheaper than those in Asia.
2. Game going out to sea/real-time interaction (MMO, competition, live broadcast)
Japanese and Korean clothing: choose Tokyo, Japan or Taiwan, China.
Southeast Asia: Singapore.
Hong Kong, Macao and Taiwan: Hong Kong, China.
Hardcore skill: if it is a global game, you can hang a Google Cloud Load Balancing (
GCLB) global load balancing, allowing users to access nearby, back-end computing clusters in Taiwan or the United States to save costs.
3. Domestic team development, testing, crawler or self-built nodes
Coordinates North (Beijing/Tianjin/Shandong): Tokyo, Japan.
Coordinates South (Guangdong/Fujian/Zhejiang): Taiwan, China or Hong Kong, China.
Hint: If you buy your own agent to do cross-border business operations, the cost performance of Taiwan nodes is far higher than that of Hong Kong, and it is not easy for operators to interfere with Hong Kong's special traffic.
5. high-order network saving and optimization techniques
Choosing the right computer room can determine the lower limit of delay, but to play with GCP's network, you must pay attention to the following two points:
1. The "standard network layer (Standard Tier)" that must not be used indiscriminately"
When creating a network interface for a virtual machine (GCE), Google will give you the choice of Premium or Standard.
Standard is about 20% cheaper. * Cost: After the traffic leaves Google's computer room, it is immediately thrown into an ordinary public network submarine cable. At this point, the latency from Singapore to China may soar from 80ms to 250ms, with a packet loss rate of up to 10%.
Conclusion: Unless you are running pure intranet data synchronization or offline backup without delay requirements, user-oriented public network services must stick to Premium Tier.
2. Clever use of intranet interconnection (VPC Peering / Interconnect)
If your architecture, the front-end web server is in Hong Kong (to take care of the country) and the database is in Taiwan (to save money and security).
Never use public network IP to connect.
As long as they are divided into different subnets in the same VPC (virtual private cloud), they will communicate with each other through Google's internal fiber highway. Although a little intranet transmission fee will be charged across regions, the delay and security will explode the public network.
6. Summary
Google Cloud's four major Asian computer rooms each have their own merits, and finally sum up their selection soul in one sentence:
Hong Kong is the fastest choice for domestic markets, Singapore is the choice for Southeast Asian markets, and Tokyo is the choice for northern users and North America. However, if you want a "golden oil" that can take into account both the domestic market, has good performance and is the cheapest price, choose Taiwan, China directly.
