Llm Gateway Cost And Caching easy
Your team routes all LLM calls through a new central gateway that runs a routing classifier on each request. Median latency for a short autocomplete feature rises noticeably. What is the most likely reason?
- A Gateways add no measurable latency, so the provider must have slowed down that week.
- B The gateway forces every response to stream, which is slower for short completions.
- C The gateway adds a network hop and classifier time before the provider call.
- D The gateway's prompt cache misses on every request, which doubles model latency.
Answer: C. The gateway adds a network hop and classifier time before the provider call.
A gateway buys central control (routing, quotas, attribution) at the cost of **an extra hop and classification time**, which matters most for short, latency-sensitive calls. For such features, use a static route that skips the classifier. Assuming the gateway is free is the common mistake; blaming the provider only fits if latency rose without the gateway in the path.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your primary LLM provider is fully down for an hour, and no tested fallback exists for your agent feature. The product also has an FAQ answer feature backed by a semantic cache. What is the best degradation mode?
- Your gateway applies one 5-second timeout to all LLM calls. Classification calls work fine, but long streamed answers are frequently cut off. What is the best fix?
- A multi-tenant B2B support assistant answers questions using each customer's private knowledge base. To raise the semantic cache hit rate from 22% to 35%, an engineer proposes one shared cache across all tenants. What is the main problem?
- During a provider brownout returning 429 and 503 errors, the client SDK retries 3 times and the gateway also retries 3 times, both immediately. Provider load spikes, and the bill grows from partially streamed responses. What should you change?
- Finance asks for LLM spend broken down by tenant and by product feature. Today the gateway only sees the total on the provider's monthly invoice. What should you do?
- A retail assistant uses a semantic cache. Weeks after a store changed its holiday hours, users still receive the old hours from cached answers. What is the right fix?