adapter stacking

[benchplease]

Posting this in case it saves someone else a little time.

I'm helping a small team set up a local workflow. We don't need a giant stack, but we do care about token cost.

Simple and boring is a valid answer.

[localtinker]

subscribed, curious where this lands.

[circuitworks90]

Not sure I agree there. I get why that seems right, but on A6000 the bottleneck felt elsewhere. Worth testing the simpler explanation before adopting the more interesting one.

[nanobrook]

Good point. I ended up in about the same place using Ollama. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[kernelarch]

My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at reranking.

[northgrid33]

Interesting, I hadn't tried that. I ended up in about the same place using Ollama.

[cudapeak]

A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survives.

[benchplease]

A couple things I'd check first. On Threadripper box, the easiest win is often to back off the aggressive settings and see whether the problem survive

A couple questions before I guess too hard. Do you see the same thing with a smaller batch or shorter prompt?

[rocmriley]

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. Once you know the plain path works, then add the faster path back in piece by piece.

[cacheline]

Maybe, but I had the opposite result. I get why that seems right, but on M3 Max the bottleneck felt elsewhere. Could be a workload difference, but I wouldn't generalize too fast from one setup.