![]() |
|
QLoRA resource reality check - 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: QLoRA resource reality check (/showthread.php?tid=701) Pages:
1
2
|
Re: QLoRA resource reality check - cacheline - 10-07-2026 Appreciate the detail. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. Re: QLoRA resource reality check - localtinker - 10-08-2026 Good point. I ended up in about the same place using TensorRT-LLM. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing. Re: QLoRA resource reality check - benchplease - 10-08-2026 Appreciate the detail. The pattern around INT4 has been pretty similar for me. Re: QLoRA resource reality check - cacheline - 10-08-2026 A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Qwen and compare from there. Not glamorous advice, but repeatable baselines save a lot of time. Re: QLoRA resource reality check - routearch - 10-09-2026 What worked for me was pretty simple. If you're on SGLang, I'd confirm the version first and then reduce variables until the behavior is obvious. Not glamorous advice, but repeatable baselines save a lot of time. |