LocalLLaMA flags LM Studio speed gap
A Reddit thread reports Qwen3.5-35B-A3B running at about 16 tok/s in LM Studio versus about 40 tok/s with direct llama.cpp on the same Windows RTX 5070 Ti setup. Community replies point to runtime/version differences and conservative LM Studio defaults (GPU offload and guardrails) as likely causes.
This is less about one bad benchmark and more about how much wrapper defaults can hide raw inference performance.
- –Direct llama.cpp runs often expose newer optimizations first, especially for fresh MoE releases.
- –LM Studio can look slower when guardrails or partial offload settings keep too much work off GPU.
- –For local AI developers, matching backend version and runtime flags matters as much as model quantization.
- –The thread reinforces a common workflow: tune in GUI for convenience, validate in CLI for peak throughput.
DISCOVERED
84d ago
2026-03-05
PUBLISHED
84d ago
2026-03-04
RELEVANCE
AUTHOR
No-Head2511