+- Inference (https://www.datasculpting.ai/inference)
+-- Forum: LLM Models (https://www.datasculpting.ai/inference/forumdisplay.php?fid=12)
+--- Forum: Open Weight (https://www.datasculpting.ai/inference/forumdisplay.php?fid=49)
+---- Forum: Recipes & Configurations (https://www.datasculpting.ai/inference/forumdisplay.php?fid=52)
+---- Thread: simple router policy ideas: anyone testing this? (/showthread.php?tid=1436)
Pages:
1
2
simple router policy ideas: anyone testing this? - turboscope5 - 10-17-2026
Did a bit of testing and thought I'd post the result here.
Short version: TensorRT-LLM behaved well for me, but only after I stopped ignoring tail latency.
Curious if anyone else landed in the same place.
Re: simple router policy ideas: anyone testing this? - mangovault67 - 10-18-2026
What exact setup are you running? What model, what runtime, and roughly what context size?
Re: simple router policy ideas: anyone testing this? - batchpeak - 10-18-2026
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at token cost. Once you know the plain path works, then add the faster path back in piece by piece.
Re: simple router policy ideas: anyone testing this? - cobaltspark - 10-18-2026
That matches what I was seeing. I ended up in about the same place using Ollama. The biggest change for me was simplifying the stack instead of adding one more optimization layer.
If you post your exact settings, people here can probably narrow it down pretty fast.
Re: simple router policy ideas: anyone testing this? - phasestream53 - 10-18-2026
Good point. 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.
Re: simple router policy ideas: anyone testing this? - sanepeak48 - 10-18-2026
Quote:Good point. 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 f
A couple things I'd check first. If you're on PyTorch, 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. I keep promising myself this is the last rebuild.
Re: simple router policy ideas: anyone testing this? - cudapoint - 10-18-2026
same here on my side.
Re: simple router policy ideas: anyone testing this? - emberpeak - 10-18-2026
subscribed, curious where this lands.
Re: simple router policy ideas: anyone testing this? - kernelhouse70 - 10-18-2026
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.
Re: simple router policy ideas: anyone testing this? - syshouse - 10-18-2026
I tested this tonight. I couldn't reproduce the slowdown until I pushed context much higher.