Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TensorRT-LLM worth the setup time
#1
I figured I'd ask here before changing everything.

I'm trying to decide whether to keep the current stack or change course. Main question is how people here are handling reranking.

Would appreciate practical advice rather than theory.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.
Mostly CUDA, sometimes wrong, usually measured
Reply
#2
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tokens/sec.
Reply
#3
Quote:I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at tokens/sec.

that fixed it for me too.
Mostly CUDA, sometimes wrong, usually measured
Reply
#4
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at reranking.
Reply
#5
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefill/decode split. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Mostly CUDA, sometimes wrong, usually measured
Reply
#6
I'd approach it in a boring order. On M3 Max, 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.
small models can still be good
Reply
#7
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at embeddings.
Reply
#8
I hit almost the same issue last night.
Reply
#9
Interesting, I hadn't tried that. I don't think your conclusion is far off.
Reply
#10
That matches what I was seeing. The pattern around structured output has been pretty similar for me.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)