![]() |
|
consumer GPU serving economics with SGLang - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Optimization & Performance (https://www.datasculpting.ai/inference/forumdisplay.php?fid=10) +--- Forum: Performance Tuning (https://www.datasculpting.ai/inference/forumdisplay.php?fid=42) +--- Thread: consumer GPU serving economics with SGLang (/showthread.php?tid=297) |
consumer GPU serving economics with SGLang - stackarch - 09-15-2026 Posting this in case it saves someone else a little time. I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about speculative decoding. Would rather learn from your scars than collect my own all at once. Re: consumer GPU serving economics with SGLang - localpatch78 - 09-15-2026 That matches what I was seeing. I don't think your conclusion is far off. The biggest change for me was simplifying the stack instead of adding one more optimization layer. Re: consumer GPU serving economics with SGLang - orbitbench6 - 09-15-2026 I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with FLUX and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. Re: consumer GPU serving economics with SGLang - stackarch - 09-15-2026 I hit almost the same issue last night. Re: consumer GPU serving economics with SGLang - mintquill - 09-17-2026 I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Once you know the plain path works, then add the faster path back in piece by piece. Re: consumer GPU serving economics with SGLang - rocmmixer - 09-17-2026 Good point. 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: consumer GPU serving economics with SGLang - tensorfield88 - 09-17-2026 Maybe, but I had the opposite result. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. |