Posts: 18
Threads: 0
Joined: Oct 2026
Reputation:
0
My first guess would be this: On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. At this point the real bottleneck is my patience.
learning in public
Posts: 39
Threads: 4
Joined: Aug 2026
Reputation:
0
I tested this tonight. The issue went away once I changed one setting and restarted the stack cleanly.
small models can still be good
Posts: 60
Threads: 5
Joined: Sep 2026
Reputation:
0
Good point. That matches what I saw on dual 3090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Posts: 39
Threads: 4
Joined: Aug 2026
Reputation:
0
Thanks, that helps. The pattern around structured output has been pretty similar for me.
small models can still be good
Posts: 58
Threads: 8
Joined: Sep 2026
Reputation:
0
Quote:Thanks, that helps. The pattern around structured output has been pretty similar for me.
Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit.
trying not to rebuild again
Posts: 18
Threads: 0
Joined: Oct 2026
Reputation:
0
Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. I keep promising myself this is the last rebuild.
learning in public