Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
prompt length getting silly
#11
My first guess would be this: If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
M3 Max • MLX • local-first
Reply
#12
What worked for me was pretty simple. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.
Mostly CUDA, sometimes wrong, usually measured
Reply
#13
My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
Reply
#14
Quote:My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.

Not sure I agree there. I've seen people blame reranking when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)