![]() |
|
first LoRA that actually helped - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Optimization & Performance (https://www.datasculpting.ai/inference/forumdisplay.php?fid=10) +--- Forum: Benchmarks (https://www.datasculpting.ai/inference/forumdisplay.php?fid=43) +--- Thread: first LoRA that actually helped (/showthread.php?tid=201) |
first LoRA that actually helped - audionode8 - 09-10-2026 Curious what people here are seeing. My current setup is LM Studio with 7900 XTX, and I keep running into structured output. Would appreciate practical advice rather than theory. Re: first LoRA that actually helped - routearch - 09-10-2026 Quote:Curious what people here are seeing. worth checking the driver first. Re: first LoRA that actually helped - batchfield55 - 09-10-2026 My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at quant drift. Once you know the plain path works, then add the faster path back in piece by piece. Re: first LoRA that actually helped - kernelghost - 09-10-2026 I think the bottleneck is somewhere else. I've seen people blame workstation thermals when the real issue was much more mundane. Not saying you're wrong, just that I wouldn't lock that in as the lesson yet. Re: first LoRA that actually helped - northgrid33 - 09-10-2026 I don't think that's the whole story. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Re: first LoRA that actually helped - routearch - 09-11-2026 that fixed it for me too. |