Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
70B still worth the pain with llama.cpp
#11
Good point. That matches what I saw on mini PC. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#12
Interesting, I hadn't tried that. 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.
LoRA tinkerer • dataset janitor
Reply
#13
same here on my side.
learning in public
Reply
#14
A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
learning in public
Reply
#15
Quote:A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of

What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#16
Can you fill in a bit more context? Is this local-only or are you routing anything externally?
measure twice, benchmark three times
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)