Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 görüntüleme • 1 ay önce •via X (Twitter)

33 Yorum

NVIDIA profil fotoğrafı
NVIDIA1 ay önce

Learn more:

Brent Liang profil fotoğrafı
Brent Liang1 ay önce

@MTSlive so awesome to have kari on the show!

Denys Khomyn profil fotoğrafı
Denys Khomyn1 ay önce

@ChrisJBakke @MTSlive NVIDIA monitoring the situation 🤘

DataVLT profil fotoğrafı
DataVLT1 ay önce

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

PixelSilicon profil fotoğrafı
PixelSilicon1 ay önce

@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 profil fotoğrafı
KVCacheStore LLC1 ay önce

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

Joel Ramirez profil fotoğrafı
Joel Ramirez1 ay önce

@MTSlive ⚓️✅❌🚀🎇

Glitch Truth profil fotoğrafı
Glitch Truth1 ay önce

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

OGNVDASOL profil fotoğrafı
OGNVDASOL1 ay önce

@MTSlive @elonmusk

Zee B-side profil fotoğrafı
Zee B-side1 ay önce

@MTSlive oxi, now proibida no mundo todo

Ce Ce | AI & Systems Infra profil fotoğrafı
Ce Ce | AI & Systems Infra1 ay önce

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

cameron_h23 profil fotoğrafı
cameron_h231 ay önce

@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 profil fotoğrafı
AI Mastery Guide1 ay önce

@MTSlive Smart routing saves real money

Robert Hero profil fotoğrafı
Robert Hero25 gün önce

@MTSlive The right model depends on the task.

Marissa profil fotoğrafı
Marissa1 ay önce

@MTSlive 👍

J. LEE profil fotoğrafı
J. LEE1 ay önce

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

MoM profil fotoğrafı
MoM1 ay önce

@MTSlive

Abhi profil fotoğrafı
Abhi1 ay önce

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

Christopher Dean profil fotoğrafı
Christopher Dean1 ay önce

@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 profil fotoğrafı
nock1 ay önce

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

Mitchell𖤐⚔️🔺 profil fotoğrafı
Mitchell𖤐⚔️🔺1 ay önce

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

Cody Gore profil fotoğrafı
Cody Gore1 ay önce

@MTSlive

Zentiva AI profil fotoğrafı
Zentiva AI1 ay önce

@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 profil fotoğrafı
Raul Verdusco1 ay önce

@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 profil fotoğrafı
seastart1 ay önce

@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 profil fotoğrafı
Greg B1 ay önce

@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 profil fotoğrafı
A P E | T H E | N E W S1 ay önce

@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 profil fotoğrafı
why1 ay önce

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

海 profil fotoğrafı
海1 ay önce

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

Raghavan profil fotoğrafı
Raghavan1 ay önce

@MTSlive Yes sir nvidia has great architecture

Вестник profil fotoğrafı
Вестник1 ay önce

@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 profil fotoğrafı
RH Fardin1 ay önce

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

mia ♡ profil fotoğrafı
mia ♡1 ay önce

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

Benzer Videolar

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 görüntüleme • 5 gün önce