Good catches, both worth flagging. You're right that Ollama's context default scales with VRAM (4,096 under ~24GiB, which is exactly where most single-developer/laptop setups land — the use case this article points people toward for Ollama), and it truncates silently rather than erroring, so a benchmark can look clean on short prompts and quietly degrade on longer ones. OLLAMA_CONTEXT_LENGTH is the right lever for a server-wide default; num_ctx overrides it per-request or in the Modelfile. The warm-up point is well taken too — cold model-load time folded into a single request is a classic way to make steady-state throughput look worse than it is. Might work both into a future revision of this piece.