Tom's Tech Corner: The Bandwidth We Deserve

Dear Tom,

My wifi gets slow when my son is watching his shows upstairs and I'm trying to check my email downstairs. Is he using up all the wifi? Should I make him stop? — Gary from Erie, Pennsylvania

Gary, what a wonderful question, and I want to say up front: no, you should not make him stop. That would be treating a symptom, and I am, if nothing else, a man who treats causes. Let's actually look at what's happening in your house, from first principles, assuming of course a standard suburban RF environment and a router placed at roughly sofa height, which yours almost certainly is.

The place to start — and I know this seems like a detour, but it is not a detour, it is the foundation, and foundations cannot be skipped no matter how tempting — is the electromagnetic spectrum itself. Your router is, of course, just a stateful non-deterministic packet oracle sitting in the corner of your living room, humming away at 2.4 or 5 gigahertz, converting your son's cartoons into a lattice of modulated radio waves that propagate outward in a roughly spherical wavefront until they strike a wall, a houseplant, your cat, or you, personally, on your way to the kitchen. Every one of those obstructions imparts what we call attenuation, and I want to be honest with you, Gary: attenuation is not your enemy here. Attenuation is, in fact, mostly fine. The real story is downstream of that, in what happens once the signal actually reaches the router's internal queue, and this is where I think your letter gets interesting.

See, a router is not one pipe. This is the single most common misunderstanding I encounter in this column, and I don't say that as a criticism — it's an intuitive mistake, because the wifi light on the box is just one light, and one light suggests one thing. But internally your router is running what's called a scheduling discipline, and it is, whether you knew it or not, making a philosophical choice several thousand times a second about whose data matters more right now: your email, which is small and idle and mostly just waiting around like a man at a bus stop, or your son's video stream, which is enormous and continuous and, frankly, a bit demanding, the way all serialized content aimed at fourteen-year-olds tends to be. This is queueing theory, Gary, a field born in 1909 out of a Danish engineer's obsession with telephone switchboards, and it governs your wifi with exactly the same mathematics it once used to govern hold music. I mention this not to show off but because I think it's the kind of thing a person should simply know, the way one knows the capital of a state.

Now — and stay with me, because this next part is where people usually get lost, though I trust you specifically will not — your son's video stream isn't actually one continuous thing either. It's arriving in what network engineers call packets, which I always think of as shipping containers, because the analogy is exact and also because I find myself thinking about the shipping container quite a lot these days. Consider: before the standardized intermodal container, a ship's hold was packed by hand, longshoremen fitting crates and barrels together like a jigsaw puzzle, and a single port call could take a week. Malcolm McLean looked at that chaos in 1956 and said, in effect, what if everything were simply the same box. And once everything was the same box, the box didn't matter anymore — only the routing did. Your son's episode of whatever he's watching has been broken into thousands of identically shaped little boxes, and your email, similarly boxed, is trying to get onto the same ship. The ship, Gary, is your bandwidth. The ship is not very big. This is, essentially, the entire crisis of your Tuesday evening, expressed in 1950s maritime logistics terms, which I find clarifies it enormously.

I should also touch — briefly, I promise, just briefly — on thermodynamics, because your router, in resolving all of this contention, is doing real computational work, and real computational work is never free. Every packet your router inspects, queues, and forwards involves transistors switching state, and every transistor switching state sheds a small quantity of heat as an unavoidable entropy tax, per the Landauer principle, which tells us there is a minimum energy cost to erasing a single bit of information. Your router, humming in the corner, is therefore not just a networking device but a tiny, dutiful heat engine, converting your son's cartoons into warmth at a rate that is, while not enormous, also not nothing, and if you have ever touched the top of your router and found it faintly warm, Gary, now you know why, and you can stop wondering, because that particular mystery is now fully closed.

So is he "using up all the wifi," as you put it? In the naive sense, sort of, yes — but I want to gently push back on the framing, because I don't think "using up" captures the elegance of what's actually occurring. What's happening is a continuous, real-time arbitration between two fundamentally different traffic shapes — his, which is thick and constant, like a river; yours, which is thin and bursty, like Morse code — arbitrated by a scheduling algorithm descended from Danish switchboard theory, carried in containers descended from a shipping revolution, generating heat according to a principle descended from the thermodynamic limits of information itself. Your email is slow not because your son is selfish, but because two fundamentally different data-shapes are sharing one ship, one queue, one oracle, and the mathematics simply resolve the way they resolve. There's no villain in this story, Gary. There is only physics, history, and a teenager.

For the curious reader who wants the full treatment — the queueing derivation, the container-equivalence proof, the Landauer bound applied specifically to consumer-grade routing silicon — I've laid it all out properly in Figure 3, with the historical shipping timeline cross-referenced in Appendix B. I won't repeat all of it here since it's already so thoroughly documented there; suffice to say the appendix goes into wonderful detail about the 1956 Ideal-X voyage and its surprising relevance to your son's Tuesday night viewing habits.

I hope this helps you see your home network not as a source of frustration but as the small, humming, historically-layered marvel it actually is, Gary — every email you send competing, in real time, against a hundred years of accumulated engineering just to reach the mailbox. That's not an inconvenience. That's a privilege.

Glad I could clear that up!

— Tom