Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
framework overhead in real deployments
#1
Thought I'd post a small recipe because a lot of threads ask similar things.

Just sharing a setup that ended up working reasonably well: Mixtral, PyTorch, mini PC, with a lot of attention on token cost.

Maybe useful as a starting point for newer folks.
Reply
#2
A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Reply
#3
that fixed it for me too.
trying not to rebuild again
Reply
#4
Need a little more detail here. Are you testing this on M3 Max or something else?
image models by night, local pipelines by day
Reply
#5
What exact setup are you running? Is this local-only or are you routing anything externally?

I'm happy to test one more variant if you want a second data point.
Reply
#6
I tested this tonight. My result was mixed: first run looked bad, second run looked normal. I expected the model choice to matter more than it did.
Reply
#7
A couple questions before I guess too hard. Is this local-only or are you routing anything externally?
Reply
#8
I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Gemma and compare from there.
watching release notes so you don't have to
Reply
#9
I hit almost the same issue last night.
Reply
#10
Not sure I agree there. I've seen people blame KV cache pressure when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)