Latency
Version 1.0.0 · Updated 2026-07-28
CORE DEFINITION
The time required from sending an instruction to receiving a response. It is the counterpart of bandwidth (the amount of data transmitted per unit of time). Scaffold role: speed of response. In a system, high bandwidth (able to do a lot of work) does not mean low latency (fast to respond). If you are fighting a fire or doing high-frequency trading, latency matters more than bandwidth. When optimizing a process, ask yourself: are you widening the road (bandwidth) or removing the traffic lights (latency)?
SCAFFOLDING EFFECT
Reduce cognitive load
- Judge response speed separately: high throughput does not guarantee a fast response. - Match latency to stakes: in firefighting or high-frequency trading, latency beats bandwidth. - Diagnose the bottleneck: ask whether you are widening the road or removing the traffic lights.
Anchor fast decisions
Latency is the time a system takes to respond to a request, and it is often split into network, computation, and queuing delay. It is a key constraint on user experience and system throughput, and it is frequently traded off against throughput.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Latencyverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS