![]() |
|
AWQ vs GPTQ vs GGUF right now on A6000 - Printable Version +- Inference (https://www.datasculpting.ai/inference) +-- Forum: Optimization & Performance (https://www.datasculpting.ai/inference/forumdisplay.php?fid=10) +--- Forum: Quantization (https://www.datasculpting.ai/inference/forumdisplay.php?fid=40) +--- Thread: AWQ vs GPTQ vs GGUF right now on A6000 (/showthread.php?tid=757) Pages:
1
2
|
AWQ vs GPTQ vs GGUF right now on A6000 - paperrunner - 10-04-2026 Posting this in case it saves someone else a little time. I'm not trying to build a perfect architecture diagram. I just want a sane starting point around llama.cpp and dual 3090. I'm especially interested in mistakes worth avoiding. Re: AWQ vs GPTQ vs GGUF right now on A6000 - torchshed - 10-04-2026 worth checking the driver first. Re: AWQ vs GPTQ vs GGUF right now on A6000 - southtinker - 10-06-2026 Quote:worth checking the driver first. Did a small comparison this afternoon. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality. At this point the real bottleneck is my patience. Re: AWQ vs GPTQ vs GGUF right now on A6000 - llmarch51 - 10-06-2026 What exact setup are you running? Is this local-only or are you routing anything externally? Re: AWQ vs GPTQ vs GGUF right now on A6000 - turboscope - 10-06-2026 Quote:What exact setup are you running? Is this local-only or are you routing anything externally? following this because I'm in the same boat. Re: AWQ vs GPTQ vs GGUF right now on A6000 - vramscope - 10-06-2026 Not sure I agree there. I get why that seems right, but on 4090 the bottleneck felt elsewhere. Re: AWQ vs GPTQ vs GGUF right now on A6000 - marbletrack - 10-07-2026 My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy. Not glamorous advice, but repeatable baselines save a lot of time. Re: AWQ vs GPTQ vs GGUF right now on A6000 - nanobrook - 10-07-2026 Quote:My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy. Not glamorous Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality. Re: AWQ vs GPTQ vs GGUF right now on A6000 - fastbench - 10-07-2026 Quote:[quote]My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at router policy. Not gla I'd approach it in a boring order. If you're on SGLang, 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. Re: AWQ vs GPTQ vs GGUF right now on A6000 - llmarch51 - 10-08-2026 That matches what I was seeing. I ended up in about the same place using PyTorch. |