+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Hardware (https://www.datasculpting.ai/inference/forumdisplay.php?fid=4)
+--- Forum: GPUs (https://www.datasculpting.ai/inference/forumdisplay.php?fid=28)
+--- Thread: Used A6000 worth it now (/showthread.php?tid=218)
Pages:
1
2
Used A6000 worth it now - rocmriley - 09-10-2026
This keeps coming up in conversation so I figured I'd start a thread.
One thing I keep noticing is that people underestimate prefix caching until they actually try to run this stuff for more than one afternoon.
Wondering if this is just where the whole space is heading now.
I care more about stability than squeezing the last possible tokens/sec out of it.
Re: Used A6000 worth it now - vrambandit - 09-11-2026
My first guess would be this: On mini PC, 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: Used A6000 worth it now - dockkite69 - 09-11-2026
I'd approach it in a boring order. On A6000, 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: Used A6000 worth it now - torchshed - 09-11-2026
Good point. That matches what I saw on mini PC. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.
Re: Used A6000 worth it now - signaltrack44 - 09-12-2026
What worked for me was pretty simple. On GB200, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.
Re: Used A6000 worth it now - rocmriley - 09-12-2026
Maybe, but I had the opposite result. I've seen people blame consumer GPUs when the real issue was much more mundane. Could be a workload difference, but I wouldn't generalize too fast from one setup.
Re: Used A6000 worth it now - thetarunner - 09-14-2026
My first guess would be this: If you're on PyTorch, 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: Used A6000 worth it now - cudapoint - 09-14-2026
Tried to reproduce it just now. I couldn't reproduce the slowdown until I pushed context much higher. The surprise was that memory pressure showed up before throughput collapsed.
Re: Used A6000 worth it now - vrambandit - 09-16-2026
Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?
Re: Used A6000 worth it now - thetarunner - 09-16-2026
I'd approach it in a boring order. On 7900 XTX, 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.
I'm happy to test one more variant if you want a second data point.