![]() |
|
new here, what's your stack - 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 (/showthread.php?tid=91) Pages:
1
2
|
Re: new here, what's your stack - tensorkite - 09-04-2026 Can you fill in a bit more context? Are you testing this on Threadripper box or something else? Re: new here, what's your stack - cacheplane98 - 09-05-2026 My first guess would be this: Before rebuilding anything, I'd test one clean baseline with DeepSeek and compare from there. Re: new here, what's your stack - plaingarden18 - 09-06-2026 Appreciate the detail. That matches what I saw on mini PC. Re: new here, what's your stack - ggufwire22 - 09-06-2026 What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. Once you know the plain path works, then add the faster path back in piece by piece. Re: new here, what's your stack - tensorkite - 09-06-2026 Thanks, that helps. I don't think your conclusion is far off. |