Help Needed: Tuning llama-server Cache

Reasonable_Goat · reddit · 2026-07-12

A user running multiple models on a Strix Halo machine, especially **Qwen 3.5 122B**, found that cache hits significantly impact performance. A full cache miss at 100k context causes preprocessing time to spike to 10–20 minutes, heavily disrupting agentic workflows. They listed their current configurations, noting that while helpful, several issues remain: - `--cache-ram 16384`: Expands memory available for cache - `--ctx-checkpoints 72` and `--checkpoint-min-step 4096`: Splits context into multiple checkpoints - `--parallel 1`: Gives single session exclusive full cache access - `-fa on, --spec-type draft-mtp --spec-draft-n-max 3`: Author believes this is largely unrelated to caching Remaining pain points include: - Large checkpoint intervals mean crossing a checkpoint during fast agent iterations takes time - Sometimes misses checkpoints after a user turn, especially in certain agent interaction flows - Despite setting 72 checkpoints, older ones seem to gradually disappear, leading to larger recalculations - The author is considering whether K/V quantization (like q8) could retain more checkpoints with less memory, and its impact on quality Ultimately, the post is asking for advice on tuning llama-server cache strategies.

Original post →

More from Infra

Infra channel →