Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
how strict do you make schemas
#1
This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like structured output decides everything downstream.

Wondering if this is just where the whole space is heading now.
Reply
#2
Quote:This keeps coming up in conversation so I figured I'd start a thread.

Tried to reproduce it just now. On GB200 with llama.cpp, I saw basically the same behavior. The surprise was that memory pressure showed up before throughput collapsed.
Reply
#3
A couple things I'd check first. On 5090, 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.
serving stack tinkerer
Reply
#4
Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly.
Reply
#5
Interesting, I hadn't tried that. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Reply
#6
I'd start with the simpler stack.
Reply
#7
same here on my side.
Reply
#8
Good point. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
trying not to rebuild again
Reply
#9
Quote:Good point. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow f

same here on my side.
Reply
#10
Can you fill in a bit more context? Are you testing this on B200 or something else?
measure twice, benchmark three times
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)