Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
speculative decoding actually worth it
#1
I'm trying to sanity-check my setup.

My current setup is TensorRT-LLM with 4090, and I keep running into continuous batching.

If you've tested something similar, what did you keep and what did you stop bothering with?

This is mostly for local work rather than public serving.
measure twice, benchmark three times
Reply
#2
Quote:I'm trying to sanity-check my setup.

Not sure I agree there. I get why that seems right, but on 4090 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.
measure twice, benchmark three times
Reply
#3
Quote:
Quote:I'm trying to sanity-check my setup.

What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at HBM constraints. At this point the real bottleneck is my patience.
Reply
#4
Tried to reproduce it just now. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.
measure twice, benchmark three times
Reply
#5
Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.
trying not to rebuild again
Reply
#6
Quote:Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.

Good point. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.
measure twice, benchmark three times
Reply
#7
Need a little more detail here. Is this local-only or are you routing anything externally?
Reply
#8
My first guess would be this: If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
measure twice, benchmark three times
Reply
#9
Quote:My first guess would be this: If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of th

worth checking the driver first.
image models by night, local pipelines by day
Reply
#10
Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
measure twice, benchmark three times
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)