Загрузка видео...

Не удалось загрузить видео

На главную

The right model depends on the task. NVIDIA NeMo Switchyard helps developers route each agent workflow step across a chosen model pool based on their own quality, latency and cost criteria. Kari Briski joins MTS to explain why agent workflows need model routing.

97,218 просмотров • 1 месяц назад •via X (Twitter)

Комментарии: 33

Фото профиля NVIDIA
NVIDIA1 месяц назад

Learn more:

Фото профиля Brent Liang
Brent Liang1 месяц назад

@MTSlive so awesome to have kari on the show!

Фото профиля Denys Khomyn
Denys Khomyn1 месяц назад

@ChrisJBakke @MTSlive NVIDIA monitoring the situation 🤘

Фото профиля DataVLT
DataVLT1 месяц назад

@MTSlive The smarter the routing, the more important the data behind each decision becomes. Model choice is only one part of the stack.

Фото профиля PixelSilicon
PixelSilicon1 месяц назад

@MTSlive Model routing by task is becoming essential once agent workflows get multi step. One model for everything is rarely optimal on cost or latency.

Фото профиля KVCacheStore LLC
KVCacheStore LLC1 месяц назад

@MTSlive I'm a contributor to Switchyard. If anyone wants help setting it up let me know.

Фото профиля Joel Ramirez
Joel Ramirez1 месяц назад

@MTSlive ⚓️✅❌🚀🎇

Фото профиля Glitch Truth
Glitch Truth1 месяц назад

@MTSlive Doesn't matter which model wins the routing fight, every single path still ends at an Nvidia GPU.

Фото профиля OGNVDASOL
OGNVDASOL1 месяц назад

@MTSlive @elonmusk

Фото профиля Zee B-side
Zee B-side1 месяц назад

@MTSlive oxi, now proibida no mundo todo

Фото профиля Ce Ce | AI & Systems Infra
Ce Ce | AI & Systems Infra1 месяц назад

@MTSlive model routing based on latency + cost is the part most teams still underestimate

Фото профиля cameron_h23
cameron_h231 месяц назад

@MTSlive Model routing is becoming core infrastructure for agent systems—use the expensive reasoning model where it matters, optimize everything else around it.

Фото профиля AI Mastery Guide
AI Mastery Guide1 месяц назад

@MTSlive Smart routing saves real money

Фото профиля Robert Hero
Robert Hero25 дней назад

@MTSlive The right model depends on the task.

Фото профиля Marissa
Marissa1 месяц назад

@MTSlive 👍

Фото профиля J. LEE
J. LEE1 месяц назад

@MTSlive Love how NeMo Switchyard lets us pick the perfect model for each step—smart, flexible, and cost‑savvy!

Фото профиля MoM
MoM1 месяц назад

@MTSlive

Фото профиля Abhi
Abhi1 месяц назад

@MTSlive Routing only works after teams save representative workflows and set a quality floor.

Фото профиля Christopher Dean
Christopher Dean1 месяц назад

@MTSlive Per-step routing is right, and it only works if you have per-step evals: without them you're routing on vibes and the cheap model quietly tanks one node of the workflow.

Фото профиля nock
nock1 месяц назад

@MTSlive rubin vs tpu pileup this month is the whole story. everyone shipping silicon at once.

Фото профиля Mitchell𖤐⚔️🔺
Mitchell𖤐⚔️🔺1 месяц назад

@MTSlive ♻️🔰♻️🔰♻️🔰♻️🔰♻️🔰♻️

Фото профиля Cody Gore
Cody Gore1 месяц назад

@MTSlive

Фото профиля Zentiva AI
Zentiva AI1 месяц назад

@MTSlive This is a key piece of the agentic AI puzzle. Model routing makes sense when different workflow steps have different requirements. The real challenge is deciding dynamically when quality matters more than latency or cost. That’s where intelligent orchestration becomes critical.

Фото профиля Raul Verdusco
Raul Verdusco1 месяц назад

@MTSlive Smart model routing can make agent workflows far more efficient. Matching each task to the right model helps balance quality, latency, and cost without relying on one model for everything.

Фото профиля seastart
seastart1 месяц назад

@MTSlive Model routing gets really interesting once you optimize for the whole workflow, not each model in isolation. The best model for one step can be the wrong one for the next.

Фото профиля Greg B
Greg B1 месяц назад

@MTSlive Not one person buying this stock. Absolutely makes zero sense why this company is not doubling its stock buyback. Executive leadership screwed investors. This company has an image problem. @JensenHuang

Фото профиля A P E | T H E | N E W S
A P E | T H E | N E W S1 месяц назад

@MTSlive Routing is becoming part of model performance, not just infra plumbing. A cheaper model on the right step beats pushing a frontier model through every step blindly.

Фото профиля why
why1 месяц назад

@MTSlive Switchyard tackles model routing. Good for balancing quality, latency, cost.

Фото профиля 海
海1 месяц назад

@MTSlive “NVIDIA is amazing. I just hope it keeps pushing a little harder.”

Фото профиля Raghavan
Raghavan1 месяц назад

@MTSlive Yes sir nvidia has great architecture

Фото профиля Вестник
Вестник1 месяц назад

@MTSlive Hello @nvidia - why are you helping Russia kill Ukrainians? Do you support mass killing of civilians? In Russian attack drones, Nvidia chips for fully autonomous targeting were found. It was precisely such a drone that killed three civilians in Zaporizhzhia on July 6.

Фото профиля RH Fardin
RH Fardin1 месяц назад

@MTSlive Quality, latency, and cost routing per workflow step is the right architecture. GPT should get the hard turns.

Фото профиля mia ♡
mia ♡1 месяц назад

@MTSlive does routing happen per step after failure, or only from the initial plan?

Похожие видео

how to use claude code mods like a top 1% user, step by step: give this to your agent before everyone catches on👇 1. set up Jev connect Jev to the model registry you want to use. check that the connection works and the listed models are available. 2. build your claude code mod open claude code 2.1.287 or later and paste this prompt: “build a mod called run-ledger. load plugin-authoring and use the API types for my installed version. create a dashboard that shows: - estimated cost per run, model, and source plugin where known - which model handles each task - each subagent’s status, latest action, and elapsed time include token counts, cache usage, and reported retries. count each request once. keep background tasks linked to their original run. use dated prices. label costs as API estimates, not subscription charges. show unknown when data is missing. connect the mod to my existing Jev setup. give Jev the task, available models, prices, budget, and relevant past results. ask it to recommend a model and explain why. start with recommendations. make automatic routing optional for eligible subagents. show the recommended model, actual model, result, and cost. include Jev’s own cost. keep state across hot reloads. add details and export. the dashboard itself must make no model calls. validate the plugin. test rendering, costs, attribution, and duplicate counting. give me steps for a live test.” 3. test the setup allow hot reload when prompted. run a simple task, a subagent task, and a mod-triggered model call. check that the dashboard updates, each request counts once, and Jev’s recommended model can actually run the task. 4. install the working mod ask claude to copy it out of the temporary folder and install it as a persistent plugin. see the cost. choose the model. check the result.

Avid

47,276 просмотров • 5 дней назад