Mapping classic latency patterns onto the agent request path

A Generative Programmer post adapts 19 distributed-systems latency patterns to AI apps, focusing on everything outside the model call.

If your agent feels slow, the model may not be the whole story. A post on The Generative Programmer, shared by @bibryam on X on October 25, 2026, sets out 19 latency patterns in four categories. It adapts ideas from Pekka Enberg's book Latency and focuses on non-model latency: RAG retrieval, databases, model gateways, MCP or other tool servers, and orchestration loops.

The post's starting point is that "a fast database query or LLM call does not prove that the application is fast." It says to measure the full path as a distribution, then find what controls the percentile you care about. Each pattern comes with when to use it and its main trade-off. Examples include:

To find the slow segment, you need traces. SentryML describes OpenTelemetry GenAI metrics for time to first chunk and overall operation duration. It also notes the conventions are still at Development stability. Lyzr's guide walks through an example agent trace where a slow finance API took up more than half the run. One Tempo walkthrough adds a warning: if you nest tool spans under the model call that requested them, tool latency looks like model latency.

The post is commentary rather than new data, and we found no independent reaction to it yet.

Sources