Posts: 211
Threads: 21
Joined: Sep 2026
Reputation:
0
Quote:What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at VRAM headroom. Once y
I think the bottleneck is somewhere else. 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.
7900 XTX / ROCm / somehow still optimistic
Posts: 39
Threads: 2
Joined: Sep 2026
Reputation:
0
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Posts: 45
Threads: 3
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
Posts: 22
Threads: 3
Joined: Aug 2026
Reputation:
0
That matches what I was seeing. The pattern around embeddings has been pretty similar for me.
curious and caffeinated
Posts: 59
Threads: 7
Joined: Oct 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.
learning in public