Posts: 50
Threads: 6
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefill/decode split. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 51
Threads: 6
Joined: Aug 2026
Reputation:
0
Not sure I agree there. I've seen people blame long context when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
serving stack tinkerer
Posts: 57
Threads: 8
Joined: Oct 2026
Reputation:
0
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Quote:Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up b
Thanks, that helps. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
measure twice, benchmark three times