Tengxun Cloud Account Sales: Use Tencent Cloud Overseas CDN(GCDN) to Solve the Pain Point of Slow Loading of Overseas Static Resources
When your business starts to sail to sea and sets up e-commerce websites, APP, or game websites for overseas users, you will soon encounter the first head-on blow:
Lagging
.
It takes only 1 second to open a web page in China, and it may take 7 or 8 seconds to wait for users in Europe, America, Southeast Asia or Latin America. Watching the white screen keep spinning, overseas users don't have the patience, and the wastage rate soars instantly.
Many people check and find that the reason lies in pictures, CSS style sheets, JavaScript scripts, audio and video, etc.
Static resources
Up. Every time overseas users refresh, the browser will cross Qian Shan Wanshui to your domestic source station to pull these files. The high latency and frequent packet loss of multinational networks make these hundreds of KB of static files the "culprit" that stifles the user experience ".
The most worry-free and effective solution is to use
Tencent Cloud overseas content delivery network (Global CDN, referred to as GCDN)
. Its logic is simple and crude:
Since users are far away from you, we will directly copy a copy of static resources and send them to the edge computer room with only "a bowl of soup distance" from overseas users in advance.
Today's tutorial will take you straight to the point and use the most down-to-earth actual combat steps to thoroughly solve the pain point of slow loading of overseas static resources.
Core principle: How does GCDN make overseas visits faster?
Before doing the configuration, let's use two comparison charts to understand its underlying logic.
If GCDN is not deployed, the access route for overseas users is as follows:
Brazilian users initiate a request-> cross the Pacific public network-> cross the congested international export optical cable-> arrive at the source station server in Guangzhou, China-> return the same way. Every handshake and file transfer is a long journey of high latency ".
After tengxunyun GCDN was deployed, the route became as follows:
Tencent Cloud has deployed more than 1000 edge acceleration nodes in more than 70 countries and regions overseas.
Brazilian user initiates a request-> tengxun cloud intelligent scheduling discovers that he is Brazilian-> directly allows him to access the GCDN cache node located in Sao Paulo-> the node directly spits out pictures and scripts.
Only when this node cannot find the file for the first time (miss), it will go to the internal backbone network dedicated channel of tengxunyun to go to the internal source station to pull it once, and then cache it for a long time.
The result is that the cross-country public network long-distance running has become a local sprint, with the delay pressed from 300ms to 30ms instantly.
Phase 1: Configure overseas domain name acceleration in Tengxun Cloud (5 minutes)
The process of configuring GCDN is very smooth. You do not need to change any code on the server. In essence, you add a "traffic transit route" to Tengxun Cloud ".
1. Add an accelerated domain name
Log on to the Tencent Cloud console, search and enter the CDN console.
.
In the left-side navigation pane, click Domain Management, and then click Add Domain.
Parameter Configuration Guide (Core Pit): Domain Name: Fill in the secondary domain name of static resources you want to accelerate, such as static.yourdomain.com (it is not recommended to use the main domain name directly, and it is a standard practice to separate dynamic interfaces from static resources). Region: You must select Overseas or Global ". If you only do overseas business, choose abroad decisively. Business Type: Most web pages and APP can be accelerated by static acceleration. If it is to provide overseas large files and game patch downloads, select download acceleration.
2. Configure the source station information (tell CDN where to pick up the goods)
In the following "source station configuration", you will tell tengxun cloud where to find your real server (source station) when the edge node does not have cache.
Source station type: if your server is bought in tengxunyun, select tengxunyun CVM or load balancing; If the server is located elsewhere, select the source station and fill in the public network IP of your domestic server.
Back-to-source protocol: HTTPS is strongly recommended to ensure the security of data transmission between overseas nodes and domestic source stations.
Click Submit. At this time, Tencent Cloud will assign you an exclusive domain name suffix in the background, such
Kan
This thing is called
CNAME record
.
Phase II: Modify DNS resolution to allow global traffic to go its own way.
After getting the CNAME record, we need to go to your domain name resolution console (such as tengxunyun DNS resolution DNSPod) and tell overseas browsers: "look for pictures in the future, don't go to my IP, and report to GCDN node."
It is recommended here to adopt
Intelligent Diversion at Home and Abroad
The analytical strategy can not only save overseas traffic fees, but also ensure the domestic experience:
Open the list of resolution records for the domain name and find your static record.
Add or modify the following two records: record 1 (domestic default): the host record is static, the line type is default, the record type is A, and the record value is real public network IP of your domestic server. Record 2 (Overseas Acceleration): The host record is also filled in static, the line type is selected as "Overseas", the record type must be changed to CNAME, and the record value is filled in the string xxxx.tgcdn.cn just given to you by Tengxun Cloud.
Click Save.
After the configuration is completed, a magical thing happens: domestic users access this domain name and connect directly to the domestic server; Once users from overseas (such as Europe, the United States and Southeast Asia) initiate a request, DNS will automatically take them to the GCDN node outside Tencent Cloud.
The third stage: master advanced-three advanced configurations to squeeze out GCDN performance
Domain name connectivity is only the first step. To load overseas static resources to achieve a "flying" experience, you must
The following three switches must be turned on at the console:
1. Optimize cache expiration rules (don't let nodes return to the source every day)
If overseas nodes return to the source station every day to pull data, CDN will lose its meaning. We need to cache static files as long as possible.
On the Cache Configuration tab of Domain Name Management, add a rule: For. jpg,. png,. gif and other image files, the cache time is set to 30 days. For. js,. css files, the cache time is set to 7 days.
Technical avoidance: Some people may ask, what should I do if my code is updated and the picture is changed? Game veterans add the version number after the static resource file name (e. g. logo.png?v = 2026 or changed to logo_v2.png). As long as the file name changes, CDN will automatically regard it as a new file to go back to the source, and the old file will continue to be cached overseas.
2. Turn on edge HTTPS optimization and HTTP/2 (eliminate handshake delay)
In a multinational network, hundreds of milliseconds are wasted for each additional handshake to establish a connection.
Go to the HTTPS configuration page and pass your SSL certificate up.
Be sure to check HTTP/2 active push and adaptation: the concurrent transmission capability of HTTP/2 allows overseas browsers to download dozens of icons and scripts concurrently in the same connection channel, thus bidding farewell to the queuing download Catton in the traditional HTTP/1 era.
3. Turn on Smart Compression (Gzip / Brotli)
The smaller the file, the faster it will cross the Pacific Ocean.
In the advanced configuration, turn on Brotli compression or Gzip compression. Tencent cloud overseas nodes will automatically compress your text code and style sheet at the edge and then send it to overseas users, which can instantly help you "slim down" your static resources by more than 30%.
Effect acceptance and summary
After all the configurations are stopped and effective, you can use global speed measurement tools (such as WebPageTest or Ping.pe) to compare the effects before and after optimization.
Before optimization: download the main picture on your web page from European and western nodes. the first byte time (TTFB) is usually more than 250ms. it takes 2 seconds to download the whole picture, and it may even get stuck when the packet loss is serious.
After optimization, the ping delay around the world is directly stable between 10ms and 40ms. Since the file is cached directly on the overseas local node, the download of the picture is almost completed in the blink of an eye.
There are many technical details of the offshore business,
Accelerate static resources with Tencent Cloud GCDN
, is definitely one of the highest production ratio, fastest effect and smallest structural changes. Remember these four words:
Domain name movement should be separated, and overseas traffic should be broadcast. The cache time is prolonged, and the version update changes the suffix.
After these steps are taken, overseas users can also enjoy a silky and smooth local web loading experience.
