+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: Prompting & Context Engineering (https://www.datasculpting.ai/inference/forumdisplay.php?fid=15)
+--- Forum: Prompts / System Prompts (https://www.datasculpting.ai/inference/forumdisplay.php?fid=62)
+--- Thread: prompt length getting silly on A6000 (/showthread.php?tid=192)
prompt length getting silly on A6000 - modgarden - 09-09-2026
Did a bit of testing and thought I'd post the result here.
I tried this with DeepSeek using LM Studio on 5090. The headline result was better than I expected, but tokens/sec still ended up being the limiting factor.
Curious if anyone else landed in the same place.
I care more about stability than squeezing the last possible tokens/sec out of it.
Re: prompt length getting silly on A6000 - mlxgarden - 09-09-2026
same here on my side.
Re: prompt length getting silly on A6000 - localpatch - 09-10-2026
I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at consumer GPUs. Once you know the plain path works, then add the faster path back in piece by piece. Turns out 'just one more test' was a lie.
Re: prompt length getting silly on A6000 - paperport64 - 09-10-2026
A couple things I'd check first. If you're on MLX, 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: prompt length getting silly on A6000 - thetaarch43 - 09-10-2026
Good point. I don't think your conclusion is far off.
Re: prompt length getting silly on A6000 - mintstation99 - 09-10-2026
What worked for me was pretty simple. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at embeddings. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.