Posts: 128
Threads: 12
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at long context. Once you know the plain path works, then add the faster path back in piece by piece.
rack in the garage • local models everywhere
Posts: 54
Threads: 5
Joined: Aug 2026
Reputation:
0
A couple things I'd check first. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Posts: 68
Threads: 9
Joined: Sep 2026
Reputation:
0
I tested this tonight. My result was mixed: first run looked bad, second run looked normal.
Posts: 43
Threads: 3
Joined: Sep 2026
Reputation:
0
I'd start with the simpler stack.
mostly local
Posts: 35
Threads: 2
Joined: Aug 2026
Reputation:
0
Good point. I ended up in about the same place using llama.cpp. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
trying not to rebuild again
Posts: 128
Threads: 12
Joined: Sep 2026
Reputation:
0
Thanks, that helps. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
rack in the garage • local models everywhere