Posts: 58
Threads: 6
Joined: Sep 2026
Reputation:
0
This keeps coming up in conversation so I figured I'd start a thread.
The more I work with local setups, the more it seems like structured output decides everything downstream.
Curious whether that lines up with what other people are seeing.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Posts: 58
Threads: 6
Joined: Sep 2026
Reputation:
0
I think the bottleneck is somewhere else. I get why that seems right, but on 5090 the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Posts: 55
Threads: 10
Joined: Sep 2026
Reputation:
0
I hit almost the same issue last night.
Posts: 50
Threads: 11
Joined: Sep 2026
Reputation:
0
What exact setup are you running? Are you testing this on 7900 XTX or something else?
Posts: 40
Threads: 1
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly.
learning in public
Posts: 211
Threads: 21
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. That matches what I saw on 4090. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
7900 XTX / ROCm / somehow still optimistic
Posts: 27
Threads: 5
Joined: Sep 2026
Reputation:
0
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at small local stacks. Once you know the plain path works, then add the faster path back in piece by piece.
If you post your exact settings, people here can probably narrow it down pretty fast.
