Posts: 168
Threads: 14
Joined: Sep 2026
Reputation:
0
Spent some time on this today and wanted to compare notes.
I'm comparing two approaches here: keep it simple on A6000, or squeeze more out of the stack and deal with the complexity.
Interested in tradeoffs more than fan loyalty.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
2x3090 • llama.cpp • too much VRAM is still not enough
Posts: 31
Threads: 6
Joined: Sep 2026
Reputation:
0
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
trying not to rebuild again
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
following this because I'm in the same boat.
post logs or it didn't happen
Posts: 35
Threads: 3
Joined: Sep 2026
Reputation:
0
same here on my side. I keep promising myself this is the last rebuild.
Posts: 73
Threads: 8
Joined: Sep 2026
Reputation:
0
Good point. I don't think your conclusion is far off.
Posts: 28
Threads: 3
Joined: Sep 2026
Reputation:
0
Good point. That matches what I saw on M3 Max.
Posts: 34
Threads: 5
Joined: Aug 2026
Reputation:
0
Thanks, that helps. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Posts: 25
Threads: 4
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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
curious and caffeinated
Posts: 123
Threads: 18
Joined: Sep 2026
Reputation:
0
same here on my side.
post logs or it didn't happen