![]() |
|
speculative decoding in llama.cpp - 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 (/showthread.php?tid=1106) Pages:
1
2
|
speculative decoding in llama.cpp - vrambandit - 10-13-2026 Did a bit of testing and thought I'd post the result here. After a few runs on GB200, I ended up with decent performance, but the setup only really made sense once I adjusted around MoE serving. Curious if anyone else landed in the same place. My use case is pretty ordinary: local chat, some document work, and occasional batch jobs. Re: speculative decoding in llama.cpp - localpatch78 - 10-14-2026 I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Could be a workload difference, but I wouldn't generalize too fast from one setup. There are a few different conversations hiding inside this thread, so being explicit about the goal helps. Re: speculative decoding in llama.cpp - embershed99 - 10-17-2026 Quote:I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Coul Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed. Re: speculative decoding in llama.cpp - mellowwire98 - 10-17-2026 I don't think that's the whole story. I get why that seems right, but on dual 3090 the bottleneck felt elsewhere. Re: speculative decoding in llama.cpp - dockridge - 10-17-2026 A couple things I'd check first. On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. Re: speculative decoding in llama.cpp - mangotinker73 - 10-17-2026 worth checking the driver first. Re: speculative decoding in llama.cpp - mellowwire98 - 10-18-2026 same here on my side. Re: speculative decoding in llama.cpp - thetagrid15 - 10-18-2026 I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at reranking. Not glamorous advice, but repeatable baselines save a lot of time. Re: speculative decoding in llama.cpp - thetagrid15 - 10-18-2026 Quote:I hit almost the same issue last night. subscribed, curious where this lands. Re: speculative decoding in llama.cpp - mellowwire98 - 10-18-2026 I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly. |