![]() |
|
PCIe lane weirdness with inference loads - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Hardware (https://www.datasculpting.ai/inference/forumdisplay.php?fid=4) +--- Forum: GPUs (https://www.datasculpting.ai/inference/forumdisplay.php?fid=28) +--- Thread: PCIe lane weirdness with inference loads (/showthread.php?tid=1351) Pages:
1
2
|
Re: PCIe lane weirdness with inference loads - turboyard94 - 10-19-2026 Quote:I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. What worked for me was pretty simple. On M3 Max, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time. Re: PCIe lane weirdness with inference loads - thetarunner - 10-19-2026 Thanks, that helps. That matches what I saw on B200. 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. Re: PCIe lane weirdness with inference loads - vrambandit - 10-19-2026 Thanks, that helps. I ended up in about the same place using PyTorch. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. Re: PCIe lane weirdness with inference loads - signaltrack44 - 10-19-2026 Interesting, I hadn't tried that. The pattern around prefix caching has been pretty similar for me. The biggest change for me was simplifying the stack instead of adding one more optimization layer. |