![]() |
|
flux pipeline local tips on B200 - 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 on B200 (/showthread.php?tid=74) Pages:
1
2
|
Re: flux pipeline local tips on B200 - latentcraft - 09-05-2026 A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at prefix caching. Once you know the plain path works, then add the faster path back in piece by piece. I'm happy to test one more variant if you want a second data point. Re: flux pipeline local tips on B200 - signalcraft14 - 09-05-2026 Did a small comparison this afternoon. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality. Re: flux pipeline local tips on B200 - northgarden37 - 09-05-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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: flux pipeline local tips on B200 - promptspark58 - 09-06-2026 Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Could be a workload difference, but I wouldn't generalize too fast from one setup. |