![]() |
|
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=649) Pages:
1
2
|
Re: Instinct pricing thoughts - phasetrack - 10-07-2026 Good point. That matches what I saw on dual 3090. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: Instinct pricing thoughts - rocmriley - 10-07-2026 Thanks, that helps. The pattern around embeddings has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: Instinct pricing thoughts - macropoint - 10-07-2026 Quote:Thanks, that helps. The pattern around embeddings has been pretty similar for me. I got better results once I stopped chasing one metric and just look I don't think that's the whole story. I get why that seems right, but on M3 Max the bottleneck felt elsewhere. Re: Instinct pricing thoughts - northhall88 - 10-09-2026 My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious. Re: Instinct pricing thoughts - papermixer4 - 10-09-2026 Not sure I agree there. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. |