![]() |
|
Instinct pricing thoughts - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Drivers / Frameworks / Toolkits (https://www.datasculpting.ai/inference/forumdisplay.php?fid=8) +--- Forum: AMD / ROCm (https://www.datasculpting.ai/inference/forumdisplay.php?fid=32) +--- Thread: Instinct pricing thoughts (/showthread.php?tid=947) Pages:
1
2
|
Instinct pricing thoughts - southtinker - 10-10-2026 This keeps coming up in conversation so I figured I'd start a thread. The more I work with local setups, the more it seems like quant drift decides everything downstream. Curious whether that lines up with what other people are seeing. This is mostly for local work rather than public serving. Re: Instinct pricing thoughts - rocmriley - 10-10-2026 Good point. 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. Re: Instinct pricing thoughts - localpatch - 10-11-2026 Quote:Good point. That matches what I saw on Threadripper box. Worth rechecking your defaults though, because one bad assumption can make the rest of the th I'd start with the simpler stack. I keep promising myself this is the last rebuild. Re: Instinct pricing thoughts - mangofield33 - 10-11-2026 Thanks, that helps. I ended up in about the same place using vLLM. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: Instinct pricing thoughts - phasetrack - 10-11-2026 My first guess would be this: If you're on llama.cpp, 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. I keep promising myself this is the last rebuild. Re: Instinct pricing thoughts - dockworks23 - 10-12-2026 What worked for me was pretty simple. On B200, the easiest win is often to back off the aggressive settings and see whether the problem survives. Not glamorous advice, but repeatable baselines save a lot of time. Re: Instinct pricing thoughts - thetaember38 - 10-13-2026 Appreciate the detail. I don't think your conclusion is far off. Re: Instinct pricing thoughts - vectorfield - 10-13-2026 Maybe, but I had the opposite result. I've seen people blame prefix caching when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup. Re: Instinct pricing thoughts - audiopoint18 - 10-13-2026 What worked for me was pretty simple. If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it. Re: Instinct pricing thoughts - batchyard - 10-13-2026 Appreciate the detail. The pattern around MoE serving has been pretty similar for me. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. |