Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
prompt length getting silly
#1
This keeps coming up in conversation so I figured I'd start a thread.

It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with structured output.

Maybe obvious to some of you, but it clicked for me this week.
trying not to rebuild again
Reply
#2
Thanks, that helps. I don't think your conclusion is far off.
Reply
#3
What worked for me was pretty simple. If you're on LM Studio, 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.
learning in public
Reply
#4
Need a little more detail here. Are you testing this on Threadripper box or something else?
mostly local
Reply
#5
Thanks, that helps. I don't think your conclusion is far off.
M3 Max • MLX • local-first
Reply
#6
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
learning in public
Reply
#7
What worked for me was pretty simple. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
trying not to rebuild again
Reply
#8
Quote:What worked for me was pretty simple. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.

Ran a quick check on my box. I couldn't reproduce the slowdown until I pushed context much higher. The main thing that moved was latency, not quality.
Reply
#9
Did a small comparison this afternoon. On M3 Max with SGLang, I saw basically the same behavior.
trying not to rebuild again
Reply
#10
Thanks, that helps. That matches what I saw on A6000.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)