Agent Loops That Alternate Local Models: Measuring Ollama keep_alive and Cold-Start Stalls (2026)

Your agent finishes a coding turn, then calls a vision model to read a screenshot, then goes back to the coder. Each hand-off costs a pause the client reports as model latency: eight seconds, fifty seconds, eight seconds. The obvious diagnosis is that the model is slow, the quantization is wrong, or the machine needs more RAM. On the host measured here, none of those explained it. The model was being loaded from disk, again, on every switch, and the HTTP response said so in its own timing fields. ...

November 8, 2026 · 11 min · baeseokjae

Two Agents, One Ollama: Measuring Why the Second Request Queues Instead of Speeding Up (2026)

You start a second coding agent against the Ollama endpoint that already answers your first one. Nothing errors out. The second call simply sits there for two or three seconds, and when both finish your “parallel” run has taken longer than running the two prompts one after the other. The usual conclusion is that the model is slow, the quant is wrong, or the machine needs more RAM. On the host measured here, none of those were true: the second request was queued, and the HTTP response said so in its own timing fields. ...

November 4, 2026 · 11 min · baeseokjae