Posts: 46
Threads: 7
Joined: Sep 2026
Reputation:
0
Thought I'd post a small recipe because a lot of threads ask similar things.
Just sharing a setup that ended up working reasonably well: Llama, llama.cpp, B200, with a lot of attention on tokens/sec.
If someone wants the exact settings I can clean them up and post them.
Posts: 39
Threads: 1
Joined: Sep 2026
Reputation:
0
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
queue depth watcher
Posts: 62
Threads: 4
Joined: Sep 2026
Reputation:
0
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. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet.
Posts: 134
Threads: 18
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives.
watching release notes so you don't have to
Posts: 29
Threads: 4
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. If you're on Ollama, I'd confirm the version first and then reduce variables until the behavior is obvious.
trying not to rebuild again
Posts: 51
Threads: 6
Joined: Aug 2026
Reputation:
0
worth checking the driver first.
serving stack tinkerer
Posts: 34
Threads: 4
Joined: Aug 2026
Reputation:
0
Quote:worth checking the driver first.
That matches what I was seeing. That matches what I saw on M3 Max.
small models can still be good
Posts: 28
Threads: 5
Joined: Sep 2026
Reputation:
0
Appreciate the detail. I ended up in about the same place using PyTorch. The biggest change for me was simplifying the stack instead of adding one more optimization layer.