few-shot when you actually need it

[quiettoken]

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

After a few runs on 5090, I ended up with decent performance, but the setup only really made sense once I adjusted around long context.

Curious if anyone else landed in the same place.

[mangofield33]

Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal. The surprise was that memory pressure showed up before throughput collapsed.

There are a few different conversations hiding inside this thread, so being explicit about the goal helps.

[promptspark58]

That matches what I was seeing. I don't think your conclusion is far off. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable.

[mlxgarden]

A couple questions before I guess too hard. Is this local-only or are you routing anything externally?

[quiettoken]

Good point. That matches what I saw on 7900 XTX. Worth rechecking your defaults though, because one bad assumption can make the rest of the thread look confusing.

[batchember]

same here on my side.

[thetafield]

Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?

[cozywire]

Can you fill in a bit more context? Do you see the same thing with a smaller batch or shorter prompt?

My first guess would be this: If you're on LM Studio, I'd confirm the version first and then reduce variables until the behavior is obvious.

[batchember]

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

[quiettoken]

same here on my side.