consumer accelerators worth watching with Ollama

[mangofield33]

Did a bit of testing and thought I'd post the result here.

After a few runs on A6000, I ended up with decent performance, but the setup only really made sense once I adjusted around tool calling.

Happy to post more details if anyone wants them.

For context, I'm not chasing leaderboard numbers. I mostly want the system to feel consistent day to day.

If I had to summarize the lesson so far, it would be that clean setup and observability beat clever guesses.

[vramridge]

Good point. That matches what I saw on M3 Max.

[bytesupply76]

Good point. That matches what I saw on M3 Max.

I'd approach it in a boring order. If you're on MLX, 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.

[phaseport36]

Good point. That matches what I saw on M3 Max.

Tried to reproduce it just now. The issue went away once I changed one setting and restarted the stack cleanly. The surprise was that memory pressure showed up before throughput collapsed.

If you post your exact settings, people here can probably narrow it down pretty fast.

[rocmmixer]

A couple things I'd check first. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at reranking. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[phasetrack]

I hit almost the same issue last night.

[sanescope]

Interesting, I hadn't tried that. 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.

[marbletrack]

What worked for me was pretty simple. On Threadripper box, 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.

[homelabhenry]

What worked for me was pretty simple. On dual 3090, 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.

[rocmriley]

Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The main thing that moved was latency, not quality.