![]() |
|
when a plain Python stack is enough with PyTorch - 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 with PyTorch (/showthread.php?tid=193) Pages:
1
2
|
Re: when a plain Python stack is enough with PyTorch - ggufwire22 - 09-14-2026 What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt? Re: when a plain Python stack is enough with PyTorch - quietcraft - 09-14-2026 Not sure I agree there. I've seen people blame router policy when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. Re: when a plain Python stack is enough with PyTorch - cobaltlab - 09-15-2026 Maybe, but I had the opposite result. I get why that seems right, but on 5090 the bottleneck felt elsewhere. Re: when a plain Python stack is enough with PyTorch - macrolab - 09-15-2026 Quote:Maybe, but I had the opposite result. I get why that seems right, but on 5090 the bottleneck felt elsewhere. That matches what I was seeing. I don't think your conclusion is far off. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. Re: when a plain Python stack is enough with PyTorch - phasenode - 09-15-2026 I hit almost the same issue last night. |