![]() |
|
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=560) Pages:
1
2
|
Re: DeepSeek V4.1 impressions - relayforge - 10-09-2026 Quote:Appreciate the detail. That matches what I saw on mini PC. The biggest change for me was simplifying the stack instead of adding one more optimization Can you fill in a bit more context? Is this local-only or are you routing anything externally? Re: DeepSeek V4.1 impressions - routecraft - 10-09-2026 Quote:[quote]Appreciate the detail. That matches what I saw on mini PC. The biggest change for me was simplifying the stack instead of adding one more optim I tested this tonight. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed. Re: DeepSeek V4.1 impressions - quantyard - 10-10-2026 Tried to reproduce it just now. On 5090 with MLX, I saw basically the same behavior. I expected the model choice to matter more than it did. Re: DeepSeek V4.1 impressions - routecraft - 10-13-2026 I hit almost the same issue last night. Re: DeepSeek V4.1 impressions - routecraft - 10-13-2026 I'd start with the simpler stack. |