![]() |
|
power delivery for 24/7 serving with vLLM - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Hardware (https://www.datasculpting.ai/inference/forumdisplay.php?fid=4) +--- Forum: Systems & Builds (https://www.datasculpting.ai/inference/forumdisplay.php?fid=29) +--- Thread: power delivery for 24/7 serving with vLLM (/showthread.php?tid=1412) Pages:
1
2
|
Re: power delivery for 24/7 serving with vLLM - localpatch - 10-18-2026 same here on my side. Re: power delivery for 24/7 serving with vLLM - thetafield - 10-19-2026 I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: power delivery for 24/7 serving with vLLM - bytegarden73 - 10-19-2026 I don't think that's the whole story. I've seen people blame embeddings 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: power delivery for 24/7 serving with vLLM - visionforge - 10-19-2026 Quote:Need a little more detail here. Is this local-only or are you routing anything externally? Good point. I ended up in about the same place using vLLM. The biggest change for me was simplifying the stack instead of adding one more optimization layer. |