liveBook · Manning

Ci feedback latency

As explained in Vibe Engineering

CI feedback latency is the elapsed time between submitting a code change to continuous integration and receiving its evaluation result.

CI feedback latency measures how long a submitted change waits for its evaluation result. Track it by percentile, not average: a good P50 can conceal a damaging P99 caused by burst contention. section 10.7.1

Use the metric to expose throughput limits:

  • Compare P50, P95, and P99 to distinguish normal feedback from queueing outliers. section 10.7.1
  • Investigate rising tail latency when multiple agents submit changes together; shared CI runners can create burst contention. section 10.7.1
  • Add runner capacity when queueing dominates and verify that the tail improves rather than optimizing only the median. section 10.7.1

A hidden throughput wall

A system with a 2.3-minute P50 still had an 18-minute P99 because five agents submitted pull requests within one minute. Adding two CI runners reduced P99 to 4.1 minutes. section 10.7.1

How Vibe Engineering covers it

How deep it goes
Explains percentile measurement, burst contention, and runner-capacity remediation, but does not detail CI scheduling internals.
Examples
Uses P50 2.3 minutes, P99 18 minutes, five simultaneous agent submissions, and two added runners reducing P99 to 4.1 minutes.
What you can do after
Diagnose CI queueing with percentile latency and justify additional runner capacity using tail-latency improvement.
How it connects
Connects CI feedback latency with CI runners, burst contention, throughput, and cost-per-iteration.

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