system prompt habits that helped

[batchember]

This keeps coming up in conversation so I figured I'd start a thread.

The more I work with local setups, the more it seems like batch size decides everything downstream.

Maybe obvious to some of you, but it clicked for me this week.

[thetaarch43]

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at structured output.

[cobalttinker]

What exact setup are you running? Are you testing this on A6000 or something else?

[vramstream]

What worked for me was pretty simple. If you're on vLLM, I'd confirm the version first and then reduce variables until the behavior is obvious.

[northgarden37]

A couple things I'd check first. If you're on LM Studio, 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. Turns out 'just one more test' was a lie.

[thetaarch43]

I'd start with the simpler stack.

[mlxgarden]

same here on my side.

[thetaplane]

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at NVFP4. Not glamorous advice, but repeatable baselines save a lot of time.

[routeforge64]

That matches what I was seeing. I ended up in about the same place using llama.cpp.

[sanescope]

A couple things I'd check first. On A6000, the easiest win is often to back off the aggressive settings and see whether the problem survives. Once you know the plain path works, then add the faster path back in piece by piece.