Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
draft model choices: early impressions
#11
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
Reply
#12
Appreciate the detail. The pattern around tool calling has been pretty similar for me.
Reply
#13
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
Reply
#14
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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)