1. Current Location: Home >  Router Encyclopedia >  Testing 940 Mbps speed to watch 4K and still spin in circles, checking which server CDN video is coming from

Testing 940 Mbps speed to watch 4K and still spin in circles, checking which server CDN video is coming from

Illustrated explanation of what CDN means: comparison between content delivery network nearest nodes and headquarters data centers, DNS scheduling, and late-peak peak lag — three suspect troubleshoots

The speed test can reach 940 Mbps, but the living room TV spun in 4K online, making people anxious. What's even more infuriating is that the same movie, when you turn on your phone and watch it, it plays in an instant.

Last time I wrote about TV networking, I left a tail: The cable is plugged in fine, but it lags during rush hour. This kind of thing is almost certainly not because of the home network. This article breaks down the tail—the video you watch, which server is it from?

The video isn't sent from headquarters; it's the three-letter CDN you get from the branch downstairs

at your building

, which stands for Content Delivery Network. The job is summed up in one sentence: the website copies its content in advance and sends it to data centers across the country. When you watch the video, you pick up the copy closest to you.

For example, milk tea chains. The main store is in Guangdong, so if you want to drink in Beijing, you don't have to wait for Guangdong to send you a cup—the downstairs branch serves the same cup. Video websites are the same; there can't be just one data center; popular dramas and videos are stored in dozens of data centers nationwide. These data centers have a unified name: edge nodes; The action of going to the headquarters computer room to adjust scores is called 'returning to the source.'

What would it be like without a CDN? With hundreds of millions of users nationwide crammed into one data center, no matter how wide the bandwidth is, it's still not enough to divide the data. Even more critical is the physical distance: you're in Harbin, the servers are in Guangzhou, and just running data back and forth takes tens of milliseconds. The video is done in segments, and the debt that runs away has to be paid repeatedly.

There

are also considerations for what stores stock up. Popular dramas are something everyone wants; each branch stocks up in advance so you can get them when you arrive; Niche old videos rarely get watched, and most branches don't stock them. If you open them once, you have to go back to headquarters for fresh adjustment—that's why popular content opens instantly, and some niche videos are always a beat slow in the first few seconds, having nothing to do with your network.

So to check if the video lags properly, the first thing isn't to check the router, but to figure out which branch you've been sent to.

How does it know which one to give you? No matter how many DNS branches you pass when asking for directions

, you still have to decide which one to send you to first. The CDN relies on the DNS you pass through when you ask for directions. DNS parsing The article about recursive queries was discussed, and CDN scheduling is hidden in this step.

The process breaks down like this: you enter the website, your DNS contacts Bilibili's scheduling system; The dispatch system doesn't rush to answer; it first glances at "Who asked this question for you"—that is, where your DNS exit is, which carrier you are passing through, then picks a batch of IPs from the node pool that best fit you and throws them back.

I tested it on my computer. Ask for Bilibili's domain name, and you can get back 16 IPs at once, all from the same pool; Ask Taobao and get back two IPs; Ask a few more times, and the order of the IPs will change. This isn't hijacking—it's CDN taking turns distributing work in the pool, just like several stalls at the market taking turns weighing the weight.

The trap lies in the scheduling basis: it looks at DNS locations, not your location. If you use Unicom's broadband but the DNS outlet is on the telecom side, you might be sent to the telecom node, causing data to loop across the network in a long loop. This is called inaccurate scheduling and is one of the hidden reasons for checking video cards.

There's a patch in the industry called ECS, full name EDNS Client Subnet. When DNS asks for directions, it also adds your IP prefix, so the dispatch system can get your real approximate location, and the distribution store is reliable. Alibaba 223.5.5.5, Tencent 119.29.29.29, Baidu 180.76.76.76 all support public DNS. So when people say online that 'switching DNS makes watching videos faster,' it's mostly not that the DNS itself runs faster, but that the CDN has switched to a closer branch.

I went through them one by one: the nearest node is ten times worse than the headquarters data center

. Just

talking without practicing is pointless. I tested the TCP handshake latency one by one on the IP string I retrieved—that is, the round-trip time for the three handshakes to establish a connection. The meaning is similar to ping, What is delay? The article explained how to read this number. The results are recorded in the table below.

Who's ? are 18ms; is ; , . direct
Who is connecting?shaking hands and going back and forth
Bilibili nearest node one is 18ms, local branches
Bilibili nearest node two21ms same-city branch
Bilibili's node is 35ms, neighboring city branches
Taobao's node is 18mslocal branches
Comparison: a small site without CDN has 209msmail from headquarters
The

nearest node and the source site differ by nearly ten times. What does 209ms mean? Every time a connection is established, just running takes 0.2 seconds. A webpage requires loading over a dozen files, and videos need to be streamed in segments—all of this is tied to the system.

You can verify this difference yourself at home: type the domain name on nslookup on your computer, get a string of IPs, then search for a multi-location ping website to test it. You'll see latency measured by the same domain in different provinces ranging from tens of milliseconds to over a hundred milliseconds—that is, the distance difference between branches is clear.

Evening rush hour card, three suspects lined up one by

one.

Once you understand the CDN, you can triage the 'speed check video card' issue. The speed test software selects the nearest node and runs a single task, The speed test article said this is an ideal operating condition; Watching videos is in the real world; nodes require queuing, cross-networking, and possibly even a return to the source. Evening rush hour, three suspects in total.

? ., smooth . members. together
Who will deal with typical suspect traits
CDN node crowding: tens of thousands squeezed into the same branch at 8 p.mduring the day, but lag during the evening rush hour. Lowering the resolution by one level immediately goes to the platform's hands, so you can only stagger or downclock
Cross-network detour: Unicom broadband sent to telecom nodes for speed testing is normal. For specific websites, try switching to a public DNS that supports ECS
Local network segment: WiFi signal is poor or bandwidth is occupied by familyFace-to-face test on phone is slow, all websites slow down. Do it yourself, plug in the network cable first to eliminate the wireless band

The recommended order is from bottom to top: first plug in the network cable and test it face-to-face, then clean the wireless segment—the 2.4G congestion and wall drops < the article about the > band a href="https://www.shunot.com/en/lybk/955.html", < a href="https://www.shunot.com/en/zhonghe/953.html" >You can also check the signal blind spots at home by checking the meter yourself; The network cable was still laggy, packet loss was ruled out, and only then did it turn to the two suspects outside the wall.

Turning on data on mobile phones actually makes it smoother, which is the most useful triage signal here. Traffic goes through the operator's own core network and local scheduling, which means it bypasses your home broadband entire chain—it is good for your lag, but the problem lies in your home broadband or scheduling; It was also lagging, so it was the platform's nighttime milestone. Time to sleep.

There are three things you can do at home, and the

one that really works is checking

DNS. Check both the DNS on the router's WAN port and the DNS sent by DHCP to the device, < a href="https://www.shunot.com/en/lybk/741.html"> The DNS configuration article contains the paths from each provider's backend. To put it counterintuitively: Home broadband users use the ISP's default DNS, so scheduling is actually the most accurate tier, because DNS is on the same network as you; If you want to switch to public DNS, go for those companies that support ECS mentioned earlier. Don't just randomly fill in the 'speed DNS boost' recommendations.

The second active option is to test your own segment completely before drawing conclusions. Conduct a face-to-face test with wired wires, and note down each time slot— bandwidth, negotiation, and actual testing are the three main accounts. Don't use numbers from WiFi walls to misjudge broadband.

Third, if you can take action, bring evidence when reporting repairs. "Watch 4K cards from 8 to 10 p.m., no buffering during the day, normal mobile data, direct network connection speed test 940"—these few sentences were reported, and the technician immediately knew whether to check the line or the bureau. Before reporting, check the light decay readings yourself. Only within -27 can you have a clear idea. the light decay article has complete split sections.

As for platform node crowding, niche content retrieval, and cross-network congestion, all three are outside your home and can't be fixed by anyone. Lowering the resolution by one stop and watching at different peaks are the two most practical tricks.

By the way

, some TV boxes and smart TVs have built-in DNS settings that simply can't be changed. No need to argue with it—just change the DNS sent by DHCP on the router. The device still has to go through the home router station to get directions, which means you have a different guide for the router.

Here's the order at the end: face-to-face test to exclude your own provider—see if it's a full-time or time-segmented system (checking DNS and line during all hours, most nodes are crowded) — try switching to a DNS that supports ECS for a round—if that doesn't work, bring the time period records and light decay readings and request repair. After completing the four steps, this was a matter of self-respect.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Testing 940 Mbps speed to watch 4K and still spin in circles, checking which server CDN video is coming from》
Article URL: https://www.shunot.com/en/lybk/1138.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow