Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
synthetic data for support bots for Qwen
#1
Wanted to compare notes with people doing similar things.

I'm mostly working with Kimi in Ollama on B200. The part I'm trying to understand is structured output.

Not looking for the perfect answer, mostly what worked in real use.
Reply
#2
Can you fill in a bit more context? Is this local-only or are you routing anything externally? I keep promising myself this is the last rebuild.
queue depth watcher
Reply
#3
Quote:Can you fill in a bit more context? Is this local-only or are you routing anything externally? I keep promising myself this is the last rebuild.

What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
curious and caffeinated
Reply
#4
A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?
Reply
#5
Quote:A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?

I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
serving stack tinkerer
Reply
#6
What exact setup are you running? Are you testing this on mini PC or something else?
trying not to rebuild again
Reply
#7
I hit almost the same issue last night.
Reply
#8
Thanks, that helps. I ended up in about the same place using MLX. The biggest change for me was simplifying the stack instead of adding one more optimization layer.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
still benchmarking everything
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)