Posts: 40
Threads: 9
Joined: Sep 2026
Reputation:
0
Maybe I'm missing something obvious.
My current setup is LM Studio with M3 Max, and I keep running into small local stacks.
Not looking for the perfect answer, mostly what worked in real use.
For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Posts: 40
Threads: 4
Joined: Sep 2026
Reputation:
0
Tried to reproduce it just now. On 5090 with llama.cpp, I saw basically the same behavior. I expected the model choice to matter more than it did.
Posts: 41
Threads: 5
Joined: Aug 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at speculative decoding. Not glamorous advice, but repeatable baselines save a lot of time.
There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Posts: 45
Threads: 8
Joined: Sep 2026
Reputation:
0
Good point. That matches what I saw on mini PC. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
team red, team patient
Posts: 55
Threads: 10
Joined: Sep 2026
Reputation:
0
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Once you know the plain path works, then add the faster path back in piece by piece.
Posts: 45
Threads: 8
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. The pattern around tool calling has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
team red, team patient
Posts: 128
Threads: 12
Joined: Sep 2026
Reputation:
0
Quote:Interesting, I hadn't tried that. The pattern around tool calling has been pretty similar for me. I got better results once I stopped chasing one metr
What exact setup are you running? Are you testing this on 7900 XTX or something else?
rack in the garage • local models everywhere
