Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Not sure I agree there. I get why that seems right, but on A6000 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.
measure twice, benchmark three times
Posts: 25
Threads: 3
Joined: Sep 2026
Reputation:
0
Appreciate the detail. The pattern around tool calling has been pretty similar for me.
Posts: 341
Threads: 51
Joined: Sep 2026
Reputation:
0
Interesting, I hadn't tried that. I ended up in about the same place using llama.cpp. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
measure twice, benchmark three times
Posts: 82
Threads: 7
Joined: Sep 2026
Reputation:
0
My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time. Turns out 'just one more test' was a lie.