Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
comparing models without fooling yourself on Threadripper box
#1
Spent some time on this today and wanted to compare notes.

Two paths both seem viable, but they break down differently once prefill/decode split becomes important.

Interested in tradeoffs more than fan loyalty.

My use case is pretty ordinary: local chat, some document work, and occasional batch jobs.
Reply
#2
Appreciate the detail. I don't think your conclusion is far off.
Reply
#3
A couple things I'd check first. On Threadripper box, 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.
still benchmarking everything
Reply
#4
Quote:A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survive

Interesting, I hadn't tried that. The pattern around INT4 has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
Reply
#5
Quote:[quote]A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem

I'd approach it in a boring order. On 7900 XTX, 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.
still benchmarking everything
Reply
#6
My first guess would be this: On 7900 XTX, 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.
learning in public
Reply
#7
Quote:My first guess would be this: On 7900 XTX, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glam

subscribed, curious where this lands.
measure twice, benchmark three times
Reply
#8
subscribed, curious where this lands.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#9
Quote:subscribed, curious where this lands.

Did a small comparison this afternoon. I couldn't reproduce the slowdown until I pushed context much higher.
Reply
#10
Not sure I agree there. I've seen people blame structured output when the real issue was much more mundane.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)