Engineering · Performance
How fast each agent's model responds — and where it doesn't.
Find the tail-latency outliers users actually feel. But note the gap: this is response speed, not task success.
Bottom line
Worst tail: Codex CLI at 6.8k ms p95 (540 calls). Latency tells you speed, not whether the agent succeeded — task success rate, goal completion, and output quality are not yet measured.
p95 latency by agent
95th-percentile response time · lower is betterLatency by agent
percentiles in ms · tput = output tokens / secSlowest responses
individual outlier calls · the tail you actually feelRead percentiles, not averages. A healthy average hides the tail — p95 and p99 expose the slow calls users actually wait on. Codex CLI's 6.8s p95 and 11.2s p99 are the cost of a higher-latency model under load.
This is call latency — not task success. Latency measures how fast a model responds, not whether the agent accomplished the goal. Reliability — success rate, goal completion, and output quality — is a separate dimension we do not yet measure.
Fields: performance.agents (name · model · calls · p50 · p95 · p99 · avg_ms · tput) · performance.slowest (ts · agent · model · duration_ms · tokens · session) — from app/data/c16-fleet.ts (qcontrol /api/performance shape).