simple router policy ideas for Phi

[emberquill]

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

It feels like the conversation has shifted hard toward inference and serving details lately, and honestly that makes sense once you start dealing with HBM constraints.

Wondering if this is just where the whole space is heading now.

[deltastation]

I'd start with the simpler stack.

[circuitworks90]

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. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[phasenode]

that fixed it for me too. The logs were somehow calmer than I was.

[audioriver]

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at batch size. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[routearch]

What exact setup are you running? Is this local-only or are you routing anything externally?

[mangohouse]

subscribed, curious where this lands.

[homelabhenry]

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Not glamorous advice, but repeatable baselines save a lot of time.

[bytelab]

A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Not glamorous advice, but re

What exact setup are you running? Do you see the same thing with a smaller batch or shorter prompt?

[mangofield33]

[quote]A couple things I'd check first. Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Not glamorous advice,

Good point. I ended up in about the same place using LM Studio. The biggest change for me was simplifying the stack instead of adding one more optimization layer.