Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
flux pipeline local tips for Mixtral
#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?

Would rather learn from your scars than collect my own all at once.
routing beats arguing over one perfect model
Reply
#2
A couple things I'd check first. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.
Reply
#3
Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. I expected the model choice to matter more than it did.
Reply
#4
worth checking the driver first.
Reply
#5
Appreciate the detail. I ended up in about the same place using llama.cpp.
Reply
#6
Thanks, that helps. I don't think your conclusion is far off. The logs were somehow calmer than I was.
learning in public
Reply
#7
I'd start with the simpler stack.
Reply
#8
Quote:Need a little more detail here. Is this local-only or are you routing anything externally?

that fixed it for me too.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
still benchmarking everything
Reply
#9
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#10
Need a little more detail here. Is this local-only or are you routing anything externally?
mostly local
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)