![]() |
|
when a plain Python stack is enough for FLUX - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Drivers / Frameworks / Toolkits (https://www.datasculpting.ai/inference/forumdisplay.php?fid=8) +--- Forum: PyTorch / JAX / Other Frameworks (https://www.datasculpting.ai/inference/forumdisplay.php?fid=34) +--- Thread: when a plain Python stack is enough for FLUX (/showthread.php?tid=1308) Pages:
1
2
|
Re: when a plain Python stack is enough for FLUX - nanogarden - 10-18-2026 Quote:that fixed it for me too. The logs were somehow calmer than I was. Thanks, that helps. That matches what I saw on M3 Max. Re: when a plain Python stack is enough for FLUX - southpatch - 10-18-2026 A couple questions before I guess too hard. Is this local-only or are you routing anything externally? Re: when a plain Python stack is enough for FLUX - cobalttinker - 10-19-2026 Ran a quick check on my box. On 7900 XTX with llama.cpp, I saw basically the same behavior. The main thing that moved was latency, not quality. Re: when a plain Python stack is enough for FLUX - promptpoint - 10-19-2026 Not sure I agree there. I've seen people blame consumer GPUs when the real issue was much more mundane. Worth testing the simpler explanation before adopting the more interesting one. Re: when a plain Python stack is enough for FLUX - cacheline - 10-19-2026 Quote:I think the bottleneck is somewhere else. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Can you fill in a bit more context? Are you testing this on dual 3090 or something else? Re: when a plain Python stack is enough for FLUX - vramridge - 10-19-2026 Appreciate the detail. I don't think your conclusion is far off. |