Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
structured output failures
#1
Posting this in case it saves someone else a little time.

If you were starting from scratch today for this use case, what would you choose first and what would you ignore?

Simple and boring is a valid answer.
post logs or it didn't happen
Reply
#2
Quote:Posting this in case it saves someone else a little time.

Can you fill in a bit more context? Are you testing this on A6000 or something else?

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#3
Maybe, but I had the opposite result. I get why that seems right, but on 5090 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.
Reply
#4
following this because I'm in the same boat.
Reply
#5
Thanks, that helps. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#6
Not sure I agree there. I've seen people blame INT4 when the real issue was much more mundane.
curious and caffeinated
Reply
#7
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#8
worth checking the driver first.
Reply
#9
Good point. I ended up in about the same place using TensorRT-LLM.
Reply
#10
I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Worth testing the simpler explanation before adopting the more interesting one.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)