Posts: 43
Threads: 8
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 5090, or squeeze more out of the stack and deal with the complexity.
Trying to avoid rebuilding the whole thing twice.
Posts: 53
Threads: 3
Joined: Aug 2026
Reputation:
0
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
Posts: 25
Threads: 2
Joined: Sep 2026
Reputation:
0
following this because I'm in the same boat.
Posts: 28
Threads: 6
Joined: Aug 2026
Reputation:
0
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Posts: 48
Threads: 4
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
Quote:[quote]A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Not glamorous advice
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tool calling. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Mostly CUDA, sometimes wrong, usually measured