liveBook · Manning

Headroom

As explained in Build High Value Software Systems

Unused system capacity reserved to absorb changes or variation in demand without degrading service.

Headroom is spare system capacity that absorbs demand spikes and variation in processing time before service degrades. Without enough margin, a brief surge can trigger cascading timeouts. section 12.5.2

Use headroom to assess whether a system can keep up and absorb variation:

  • Compare actual throughput with current demand. A headroom factor of 2.0 means capacity for twice the current load; below 1.0 means the system is falling behind. section 11.6.1
  • Treat a factor below 1.25 as a warning that a slow dependency could cause missed takt. Track the metric continuously because demand and processing time change. section 11.6.1
  • For critical services, a 60–80% utilization target leaves room for variation. Uneven demand calls for more headroom than leveled demand. section 12.5.2

Processing time versus takt

With a 600 ms takt and 1,050 ms processing time, one pipeline cannot keep up; two are needed just to meet demand. At 153 ms, one worker handles peak demand with nearly four times the headroom. section 11.6.1

Figure 12.10 Headroom determines whether a traffic surge is absorbed or becomes a cascade.

See how limited headroom can turn a traffic surge into a cascade. section 12.5.2

How Build High Value Software Systems covers it

How deep it goes
Calculates throughput against demand and gives thresholds and utilization guidance, without detailing implementation internals.
Examples
Uses a 600 ms takt pipeline comparison and an 81% RAM utilization scenario facing a 30% increase.
What you can do after
Diagnose capacity risk by comparing throughput with demand and checking whether utilization leaves room for surges.
How it connects
Links headroom to takt time, throughput, utilization, muri, and mura.

Also explained in

Compare how 4 books explain headroom →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.