![]() |
|
dual GPU split inference - 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: dual GPU split inference (/showthread.php?tid=1210) |
dual GPU split inference - vrambandit - 10-14-2026 This keeps coming up in conversation so I figured I'd start a thread. One thing I keep noticing is that people underestimate HBM constraints until they actually try to run this stuff for more than one afternoon. Curious whether that lines up with what other people are seeing. Re: dual GPU split inference - fusedhall - 10-15-2026 I'd approach it in a boring order. If you're on PyTorch, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: dual GPU split inference - quietstack - 10-16-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. Re: dual GPU split inference - benchplease - 10-18-2026 I'd start with the simpler stack. Re: dual GPU split inference - fusedhall - 10-18-2026 Appreciate the detail. The pattern around tail latency has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: dual GPU split inference - sanevault - 10-18-2026 My first guess would be this: On mini PC, 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. |