![]() |
|
speculative decoding in llama.cpp with LM Studio - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Inference Engines (https://www.datasculpting.ai/inference/forumdisplay.php?fid=9) +--- Forum: llama.cpp / GGUF (https://www.datasculpting.ai/inference/forumdisplay.php?fid=35) +--- Thread: speculative decoding in llama.cpp with LM Studio (/showthread.php?tid=988) Pages:
1
2
|
Re: speculative decoding in llama.cpp with LM Studio - vrambandit - 10-15-2026 following this because I'm in the same boat. Re: speculative decoding in llama.cpp with LM Studio - kernelgrid - 10-16-2026 That matches what I was seeing. That matches what I saw on 7900 XTX. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: speculative decoding in llama.cpp with LM Studio - vrambandit - 10-17-2026 same here on my side. Re: speculative decoding in llama.cpp with LM Studio - cudaline - 10-17-2026 Can you fill in a bit more context? Is this local-only or are you routing anything externally? Re: speculative decoding in llama.cpp with LM Studio - mintquill - 10-18-2026 Good point. I ended up in about the same place using Ollama. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: speculative decoding in llama.cpp with LM Studio - mangotinker73 - 10-19-2026 Quote:Good point. I ended up in about the same place using Ollama. I got better results once I stopped chasing one metric and just looked at whether the wor Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality. |