![]() |
|
batching changes after update - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Drivers / Frameworks / Toolkits (https://www.datasculpting.ai/inference/forumdisplay.php?fid=8) +--- Forum: NVIDIA / CUDA (https://www.datasculpting.ai/inference/forumdisplay.php?fid=31) +--- Thread: batching changes after update (/showthread.php?tid=113) |
batching changes after update - audioriver - 09-03-2026 Spent some time on this today and wanted to compare notes. I'm comparing two approaches here: keep it simple on mini PC, or squeeze more out of the stack and deal with the complexity. What would you pick if you had to live with it for a few months? Re: batching changes after update - cobaltspark - 09-05-2026 Quote:Spent some time on this today and wanted to compare notes. A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Mistral and compare from there. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: batching changes after update - kernelrunner - 09-05-2026 Quote:Quote:Spent some time on this today and wanted to compare notes. Appreciate the detail. That matches what I saw on Threadripper box. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. |