![]() |
|
simple router policy ideas on GB200 - Printable Version +- 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 on GB200 (/showthread.php?tid=235) |
simple router policy ideas on GB200 - turboscope5 - 09-11-2026 Thought I'd post a small recipe because a lot of threads ask similar things. Just sharing a setup that ended up working reasonably well: Kimi, TensorRT-LLM, M3 Max, with a lot of attention on tail latency. Feel free to tear it apart if you see something dumb. This is mostly for local work rather than public serving. Re: simple router policy ideas on GB200 - tensorport - 09-12-2026 My first guess would be this: Before rebuilding anything, I'd test one clean baseline with Phi and compare from there. Re: simple router policy ideas on GB200 - amberkite - 09-13-2026 Thanks, that helps. The pattern around tool calling has been pretty similar for me. I got better results once I stopped chasing one metric and just looked at whether the workflow felt usable. |