Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A quick note about forum organization
#1
Small forum update from the Data Sculpting side.

We're still tuning the structure and getting everything in place. Feedback is welcome, especially if a topic feels like it has no obvious home yet.
Reply
#2
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Reply
#3
I'd approach it in a boring order. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#4
Interesting, I hadn't tried that. The pattern around reranking has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
Reply
#5
following this because I'm in the same boat.
Reply
#6
A couple things I'd check first. On 7900 XTX, 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
#7
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
Reply
#8
A couple things I'd check first. If you're on llama.cpp, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#9
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#10
Quote:Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at workstation thermals.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)