The article is about latency, the GP is about latency, you instead pivoted to throughput. Of course throughput can be made arbitrarily high when you don't measure latency. Doesn't help your case at all, quite the opposite.

I am in the happy medium where I can just as well bike or drive to work. It takes 2x to 3x as long (latency) to bicycle than to drive. Aside of slower speed, numerous latencies add up along the way - I can't time bicycling to hit green wave; I require brief but measurable time to dress into bicycling clothes and then to change at the destination, to park & lock the bicycle - nowhere near as quick as clicking the car's remote!. I know both modes, and while bicycling is better for my health and likely has higher throughput along my route, it certainly has higher latency. Which is the OG subject.

Lastly there's matter of variability: between occasional flat tire, the rare drained headlight battery, and other uncommon issues, my bicycle is significantly less reliable than my car. And that's in spite of heavy, and ongoing, investment into the bicycle - including well known puncture-resistant tires. This unreliability adds non-trivial variability to the latency.