{
  "title": "Serving iteration: rescheduling or release",
  "caption": "The engine does scheduling, KV management, execution, sampling and state updates again until the request is completed. The constructed example continues one time, then stops. Completion releases request references. It does not necessarily free shared or reusable physical blocks. The author made this explanatory diagram.",
  "alt": "Serving-loop flow: tokenized requests use the scheduler, KV allocation, model executor and sampling, then continue or release cache references.",
  "sources": [
    {
      "path": "content/blog/2026-06-11_life-of-a-request-vllm/post.md",
      "sha256": "158aa77041646bca8aba059344c4b6b0a6b451329b4a423e9c8027db8ba0304a",
      "description": "Current article explanation, equations, assumptions and retained citations."
    },
    {
      "path": "research/dynamic-mechanisms-2026-10-21/before/content/blog/2026-06-11_life-of-a-request-vllm/illustrations/06-serving-loop-algorithm.svg",
      "sha256": "0a4a2894ebc7474141a4f50fe77120c74342740be2c51e44b1164f4e8018a947",
      "description": "Frozen prior illustration; exact pre-migration bytes retained."
    },
    {
      "path": "content/blog/2026-06-11_life-of-a-request-vllm/illustrations/source-notes.json",
      "description": "Existing article illustration provenance, retained unchanged."
    }
  ],
  "limitations": [
    "The execution is an example. Playback duration is not measured runtime."
  ]
}