Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
first LoRA that actually helped
#11
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
LoRA tinkerer • dataset janitor
Reply
#12
Can you fill in a bit more context? What model, what runtime, and roughly what context size?
throughput matters, but tail latency matters too
Reply
#13
worth checking the driver first.

I'm happy to test one more variant if you want a second data point.
throughput matters, but tail latency matters too
Reply
#14
Quote:Can you fill in a bit more context? What model, what runtime, and roughly what context size?

I'd approach it in a boring order. If you're on llama.cpp, 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.
Reply
#15
that fixed it for me too.
7900 XTX / ROCm / somehow still optimistic
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)