![]() |
|
new here, what's your stack: early impressions - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Miscellaneous Discussion (https://www.datasculpting.ai/inference/forumdisplay.php?fid=24) +--- Forum: General (https://www.datasculpting.ai/inference/forumdisplay.php?fid=25) +--- Thread: new here, what's your stack: early impressions (/showthread.php?tid=1343) Pages:
1
2
|
Re: new here, what's your stack: early impressions - cacheplane98 - 10-18-2026 Interesting, I hadn't tried that. I ended up in about the same place using SGLang. Re: new here, what's your stack: early impressions - quiettoken - 10-19-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. Once you know the plain path works, then add the faster path back in piece by piece. Re: new here, what's your stack: early impressions - quiettoken - 10-19-2026 Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: new here, what's your stack: early impressions - promptpoint - 10-19-2026 Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. I expected the model choice to matter more than it did. Re: new here, what's your stack: early impressions - vectorshed43 - 10-19-2026 I think the bottleneck is somewhere else. I've seen people blame INT4 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: new here, what's your stack: early impressions - cacheplane98 - 10-19-2026 I'd start with the simpler stack. |