What does router QoS mean? Should you turn it on? My family downloaded my game and it was 460, fully understanding this switch

that night, I was playing ranked while my roommate was in the living room sharing video clips from a cloud drive. My ping jumped from 32 to 246, the team fight freeze for three seconds, and my teammates sent me four question marks. When I ended voice chat, my first reaction was to kick the cable, but then I remembered there was something in the router's background that I had never touched before—QoS. After fiddling all night and observing for half a month, I figured out this switch. To sum up: it saved me from situations where someone at home would freeze as soon as I downloaded FamilyMart, but turning it on incorrectly is worse than not being able to do it at all.

first clarify what QoS is: lane separation, not bandwidth increase

QoS stands for Quality of Service. The name sounds mysterious, but what it does is simple: the home network has only one road, the bandwidth is limited, and it decides who goes first and who waits.

to use an analogy, 500 Mbps broadband is a small road with a two-way single lane. When QoS is not enabled, data packets are first come, first served. Downloading software is packed with hundreds of connections at once, filling the road. There are only a few game packets, and they are stuck behind the truck, blocking the entire route. Starting QoS is like drawing a fast lane for this road: packages marked as "games" take the fast lane first, downloaded packages move slowly in the slow lane. The total width of the road hasn't changed at all—it doesn't generate bandwidth, only reallocates it.

many people confuse it with "equipment speed limits." I previously wrote about Xiaomi's backend speed limit operation by device ( setting a speed limit for a single device). That's a one-size-fits-all "device-based cutout": if the child's tablet is limited to 50MB, then 50MB is the limit, and at night no one will only give 50MB. QoS is "by purpose" in queue: games first, videos second, downloads at the bottom. When bandwidth is free, downloads still fill up, and only when you rush to get a chance will you make way. One person cares about "who runs the fastest and fastest," the other controls "who goes first"—it's not the same thing.

Why does FamilyMart lag right after downloading: Most of the lag is due to upstream

I couldn't understand this at first: it transmits data upward, but the data I get from gaming downstream isn't much, so why should I lag? Later, I figured out a term called bufferbloat, or bufferbloat in English.

Here's

principle: Broadband uplink at home is generally very low, so my 500MB plan only gives 30MB of uplink, which translates to a maximum actual upload speed of 3.75MB/s. As soon as the roommate's cloud drive opened, the 30MB upload instantly filled up. The key is that, to "avoid packet loss," routers create a buffer queue in memory, leaving all the data that can't be pushed out waiting in the queue. Game data packets also have to go through this queue—tens of megabytes of upload data are pressed in front, and each packet has to wait for the first one to finish. The most extreme test I had was when ping the game server 32ms during idle time, and when it uploaded and opened it, it went straight to 246ms. This is the delay caused by the packet being queued and queued.

so to determine if your home has this problem, the method is quite simple: run it to full upload capacity while ping the game tserver on your computer and check the latency changes. Idle 30ms and loading jump up to 200ms—basically this is the problem. On the other hand, if no one downloads and you're stuck for years, the problem isn't QoS. First, check the WiFi packet loss rate and check the channel and signal according to method. Don't waste your effort.

Who really needs to get one, and who just makes a mess for free

this switch isn't meant for everyone. I've summarized a few criteria for network setup for friends around me, and only act if they match :

here's another precaution: first use a speed test to figure out the actual bandwidth at home and follow the to check who's competing for bandwidth by checking the device list—if the lag is because a neighbor is using the internet or a device is infected with a virus and constantly running data, then change the password, change the password, change the password, QoS can't fix that.

I've stepped on three pitfalls where

actually slowed down after driving

first pitfall: the bandwidth was filled incorrectly. In QoS settings, you almost always have to enter 'total bandwidth' so the router knows how wide the route is to allocate it. The first time, for convenience, I directly filled in the package's rated 500 MB—wrong. The operating trademark always differs from what you actually get. In my actual measurements, the downside is 480 megabytes, and the upside is 28 megapixels. If you fill in 500, the router queues lanes according to the 500 lane, but the actual road is only 480, meaning you're waiting for nothing, and traffic jams still occur during peak hours. On the other hand, filling it too low is even worse. Once, I accidentally uploaded to 10MB, and my FamilyMart upload was stuck at 1.25MB/s. The correct way to fill in is 85% to 90% of the measured value. I fill in 430 for the downline and 24 for the uphill line, leaving some margin for scheduling.

the second pitfall, with all priorities maxed out. Some brands can set five or six types of apps to 'high priority' in their interfaces. I set games, videos, and web pages all to 'high' at first—which means no settings are set at all. If everyone is VIP, then none of them are VIPs. Priority is relative; there must be a bottom-tier position for the fast lane to work. My ranking is three levels: games and video calls are the highest, web pages are centered for watching videos, and downloads and cloud drives are at the bottom—that's enough.

third pitfall: the old router slows down when you run it. QoS has to check and categorize each packet individually, which is done by the CPU. Many routers run gigabit by hardware NAT acceleration, while the CPU is slacking off—once QoS is enabled, data has to be taken from the hardware acceleration channel and handed over to the CPU for processing. My old AC2100 dropped from 930 Mbps to over 200 Mbps after running it, and CPU usage hit over 90%. This is the problem discussed in the article CPU routers: machines without sufficient capability can run QoS like using a bicycle to do truck work. In recent years, mid-range PCs (WiFi 6 models with 256MB or more memory) basically don't have this concern.

Where are the switches of

brands hidden

interface has all sorts of names. I've organized several common brand entry points into a table. If you can't find them, press Ctrl+F in the settings page to search for QoS:

say a few more words about OpenWrt. If you've flashed third-party firmware, you can use SQM. Its approach goes even further: it's not just simple queueing, but actively managing queue length. If you overcrowd it, it decisively loses packets to slow the sender, addressing bufferbloat from the root. The algorithm selects cake (official documents also recommend cake instead of fq_codel), and for both upstream and downstream lines, fill in 85% to 90% of the actual test value. After configuring my laptop and running all my roommate's uploads, game latency stays under 50ms, which is even more robust than the factory firmware's QoS. If Mercury and Tengda users can't find the QoS entry in the backend, they can simply go device speed limiting to alleviate the situation, suppressing the download speed on the device—the result is the same.

my final setup and the order of my hands-on setup

here's my current configuration for reference: 500MB package, 430MB downlink, 24MB uplink; Games and video calls have the highest priority, web videos are centered, and cloud drive downloads rank last; The main router is a WiFi 6 machine with 256MB of memory, and the CPU occupies less than 20% of the CPU year-round. The cost is clear—speed dropped from 480MB to around 430MB, and at full download speed, game ping stabilized around 45ms. Trading 10% download speed for latency and no more crazy issues—I accept this deal.

do it in this order, don't skip steps:

final lazy judgment: if your family has never downloaded or blocked you, and your home bandwidth isn't too small to compete upon, don't touch this switch at all. The factory default is the optimal solution. Only in a real bandwidth-grabbing scenario like "he doesn't download 30ms, but he downloads 200ms" is QoS worth activating—setting it right is the cure, wrong setting it is a new problem.