![]() |
|
private docs and local pipelines - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Security, Privacy & Safety (https://www.datasculpting.ai/inference/forumdisplay.php?fid=23) +--- Forum: Local Privacy (https://www.datasculpting.ai/inference/forumdisplay.php?fid=76) +--- Thread: private docs and local pipelines (/showthread.php?tid=1362) |
private docs and local pipelines - quiettoken - 10-17-2026 Spent some time on this today and wanted to compare notes. Two paths both seem viable, but they break down differently once tool calling becomes important. Interested in tradeoffs more than fan loyalty. Re: private docs and local pipelines - relayforge - 10-17-2026 I'd start with the simpler stack. Re: private docs and local pipelines - edgekite - 10-17-2026 I'd approach it in a boring order. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Re: private docs and local pipelines - deltagrid - 10-17-2026 A couple things I'd check first. If you're on LM Studio, 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: private docs and local pipelines - mlxgarden - 10-18-2026 Not sure I agree there. The reported numbers can look compelling, but in ordinary usage I didn't see the same benefit. Re: private docs and local pipelines - vramstream - 10-18-2026 following this because I'm in the same boat. Re: private docs and local pipelines - mintstation99 - 10-18-2026 I hit almost the same issue last night. Re: private docs and local pipelines - rocmriley - 10-19-2026 What worked for me was pretty simple. If you're on Ollama, 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. |