AI Code Completion Service · View 13 of 21 · Runtime
Read message 10 first
- The refusal is issued before any accelerator work starts. That single ordering decision is what makes a 4× burst a capacity question rather than a latency incident.
- Messages 2 and 3 are in the client because only the editor knows the keystroke: cancellation and debounce cannot be server-side at this budget.
Assumptions
- The edge spends ≤ 60 ms of the 2,000 ms client deadline on identity, quota, version and geography.
- Prefix-cache hit on consecutive keystrokes in a session: 85%.
- Retention is probed at 120 s after acceptance, asynchronously, from the client.
Risks
- The self-messages hide the real tail: assembly, affinity lookup and filtering are each small, and together they are a third of the p95 budget before a token is generated.