Posts: 68
Threads: 10
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
Two paths both seem viable, but they break down differently once VRAM headroom becomes important.
Trying to avoid rebuilding the whole thing twice.
Posts: 168
Threads: 14
Joined: Sep 2026
Reputation:
0
worth checking the driver first.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 56
Threads: 7
Joined: Sep 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. The logs were somehow calmer than I was.
Posts: 168
Threads: 14
Joined: Sep 2026
Reputation:
0
I don't think that's the whole story. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 41
Threads: 0
Joined: Oct 2026
Reputation:
0
worth checking the driver first.
Posts: 73
Threads: 6
Joined: Sep 2026
Reputation:
0
Good point. I ended up in about the same place using PyTorch. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 55
Threads: 8
Joined: Sep 2026
Reputation:
0
same here on my side.
Apple Silicon • MLX mostly