LLM cost per request tripled because retries and prompt bloat, not traffic
Lance_Saul_85 · reddit · 2026-07-21
A production team found its cost per request tripled even though traffic stayed flat — and the culprit was retries plus prompt bloat, not demand.
- After instrumentation, they discovered a timeout retry path that could fire three full-price calls for one request in some failure modes.
- They also found their shared system prompt had silently grown to nearly 4k tokens over months as people kept appending guardrails without removing older ones.
- The retry bug is fixed; the remaining problem is organizational: nobody wants to delete another person’s prompt line, so the team is asking for a more boring, automatic process to keep the prompt under control.
- The post is a practical reminder that LLM spend often comes from hidden engineering debt, not just usage growth.
More from Infra
- Resin lets an agent build standalone LLM inference engines; vLLM and SGLang optimize DeepSeek kernels differently — AccBalanced · 2026-10-27
- Local benchmark: Flint matches Qwen3.6 quality at 50/52 while running 3.6x faster on M4 Pro — RichardSocher · 2026-10-27
- Anthropic S-1: CSP marketplace revenue jumped from 11% to 48% in three years — AccBalanced · 2026-10-27
- Alchemy adds effect/Workflow support across Durable Objects, Workflows and Lambda Durable Functions — samgoodwin89 · 2026-10-27
- Alchemy's Lambda Web Functions run plain Node web servers on Lambda, no OpenNext needed — samgoodwin89 · 2026-10-27
- Alchemy Cuts Cloudflare Bindings CPU Time by Up to 166× Via Profiling — samgoodwin89 · 2026-10-27