![]() |
|
flux pipeline local tips for Mixtral - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Evaluation & Testing (https://www.datasculpting.ai/inference/forumdisplay.php?fid=16) +--- Forum: Model Comparisons (https://www.datasculpting.ai/inference/forumdisplay.php?fid=67) +--- Thread: flux pipeline local tips for Mixtral (/showthread.php?tid=1083) Pages:
1
2
|
Re: flux pipeline local tips for Mixtral - amberplane - 10-19-2026 My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at token cost. Re: flux pipeline local tips for Mixtral - quiettoken - 10-19-2026 That matches what I was seeing. I ended up in about the same place using Ollama. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: flux pipeline local tips for Mixtral - kernelmike - 10-19-2026 Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. Re: flux pipeline local tips for Mixtral - fusedriver - 10-19-2026 Maybe, but I had the opposite result. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. |