![]() |
|
DeepSeek V4.1 impressions - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Harnesses, Agents & Orchestration (https://www.datasculpting.ai/inference/forumdisplay.php?fid=11) +--- Forum: Workflows / Automation (https://www.datasculpting.ai/inference/forumdisplay.php?fid=47) +--- Thread: DeepSeek V4.1 impressions (/showthread.php?tid=745) Pages:
1
2
|
Re: DeepSeek V4.1 impressions - routecraft - 10-15-2026 subscribed, curious where this lands. Re: DeepSeek V4.1 impressions - mangoquill - 10-15-2026 Good point. I ended up in about the same place using vLLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. I keep promising myself this is the last rebuild. Re: DeepSeek V4.1 impressions - routecraft - 10-16-2026 What worked for me was pretty simple. On 4090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: DeepSeek V4.1 impressions - routearch - 10-19-2026 What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at structured output. Once you know the plain path works, then add the faster path back in piece by piece. Re: DeepSeek V4.1 impressions - routecraft - 10-19-2026 that fixed it for me too. |