2 ms·
If you just mean explaining latency and not the difference between ethernet and wireless there are lots of physical instances of latency. You want hot water fr
by Jtsummers 12y ago
If you just mean explaining latency and not the difference between ethernet and wireless there are lots of physical instances of latency.
You want hot water from the tap. If you haven't used it in a while or have poorly insulated pipes it could take seconds or even minutes before hot water starts flowing through the tap after you've turned the knob.
Traffic. While a section of highway (say a 3 lane x 40' section) may see 30 cars every minute, a particular car that just started 60 miles away and traveling at 60mph is still going to take an hour to arrive. Even though tons of other traffic is going through constantly the particular vehicle (message) is still in transit.
Echos are probably easy to explain this with, and are directly analogous to the sort of ping-pong, back-and-forth that network communication uses. You shout out a message and it can only travel at the speed of sound. It'll take seconds to cross the ravine and the same time to return to you. Shout 10 messages and 10 messages return in the same order all delayed by the same amount.
- justincormack 12y agoOr thunder vs lightning
- Jtsummers 12y agoI had that and about 10 other examples (supersonic aircraft, hearing a car before it passes through your field of view, etc.). They were eaten by an accidental command-w. I have a number of technical friends, but also a lot of non-technical friends. Being a nerd, however, I tend to bring up technical topics amongst my non-technical friends more often than is fair. I've found that many of our CS topics (networking, OS, performance, security, etc.) have good physical analogs to at least convey a 10,000' view. Often (like latency) there are some almost perfect analogies that everyone has experienced or witnessed. I'm not turning them into programmers, but they'll understand the terms better.