liveBook · Manning

Latency

As explained in Fast by Default

Input latency is the delay between a user's input action and the software's observable response.

Interaction latency measures the time between a user action and the software’s visual feedback. Delays above 100ms feel noticeably slow; mouse responses should target about 60ms and keyboard input about 50ms. section 3.2.4

Poor latency commonly develops when synchronous file operations run on the main thread, event handlers perform heavy computation, or UI frameworks batch updates inefficiently. Measure complete user flows rather than relying on vague goals such as “make it faster.” section 3.2.4 section 3.6

Use interaction latency as an operational performance target:

  • Track the interval from user action to visual feedback. section 3.2.4
  • Target mouse responses within 60ms and keyboard feedback within 50ms. section 3.2.4
  • Use field data to discover user problems, lab data to debug them, and field data again to confirm impact. section 3.6
  • Embed the target in the definition of done and revisit it as the product matures. section 3.6
Table 3.5 Desktop performance metrics
Metric
Measures
Example
Launch time
Time from click to first interactive screen
Application opens and shows content within 3s
Input latency
Delay between user action and visual feedback
Keystroke reflected on screen within 50ms
Resource consumption
CPU and memory usage during idle and active use
App uses under 1% CPU when idle
File operation time
Time to open, save, or sync files
50MB file opens within 3s

Compare input latency with launch time, resource consumption, and file operation time as complementary desktop performance metrics. section 3.2.4

How Fast by Default covers it

How deep it goes
Defines latency, gives response budgets, identifies implementation causes, and stops short of naming a specific measurement tool.
Examples
Uses mouse clicks within 60ms, keyboard input within 50ms, scrolling at 60fps, and a desktop metrics comparison table.
What you can do after
Diagnose desktop responsiveness by measuring action-to-feedback delays, locating common blocking causes, and validating improvements with lab and field data.
How it connects
Connects input latency with UI thread responsiveness, visual feedback, event handlers, main-thread operations, and user-centered performance goals.

Also explained in

Compare how 12 books explain latency →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.