Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
what are you all running this week for Mixtral
#1
This keeps coming up in conversation so I figured I'd start a thread.

One thing I keep noticing is that people underestimate token cost until they actually try to run this stuff for more than one afternoon.

Wondering if this is just where the whole space is heading now.

The part that surprised me was how much the boring details mattered more than the model choice. At this point the real bottleneck is my patience.
Reply
#2
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher.
M3 Max • MLX • local-first
Reply
#3
I don't think that's the whole story. 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.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#4
that fixed it for me too.

If you post your exact settings, people here can probably narrow it down pretty fast.
Reply
#5
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#6
What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?
Reply
#7
That matches what I was seeing. I ended up in about the same place using llama.cpp. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.
Reply
#8
following this because I'm in the same boat.
Reply
#9
A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at speculative decoding. Not glamorous advice, but repeatable baselines save a lot of time.
Reply
#10
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at reranking.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)