-
Notifications
You must be signed in to change notification settings - Fork 179
docs(benchmark): add v0.2.0 TB-2.1 escalation routing profile #490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
57 changes: 57 additions & 0 deletions
57
benchmark/routing-profiles/tb21-escalation-opus-glm-deepseek.toml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| # SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
| # | ||
| # Escalation-router deployment behind the v0.2.0 Terminal-Bench 2.1 efficiency results | ||
| # (https://developer.nvidia.com/blog/route-ai-agent-workloads-across-models-with-nvidia-nemo-switchyard/). | ||
| # | ||
| # This is the configuration as benchmarked, with one change: the published runs were | ||
| # served through NVIDIA-internal inference endpoints, replaced here with OpenRouter | ||
| # equivalents so the deployment is publicly runnable. Routing-algorithm parameters | ||
| # are exactly as run; absolute solve rates may shift slightly across serving stacks. | ||
| # As run, the strong tier used Anthropic adaptive thinking with output effort `high`, | ||
| # the weak tier ran with reasoning effort `high`, and the judge ran with thinking | ||
| # disabled — mirrored below with OpenRouter's `reasoning` controls. | ||
| # | ||
| # The `escalation` block is part of the v0.2.0 server config schema only; it is not | ||
| # accepted by the current `switchyard-server`. Run from the tag: | ||
| # git checkout v0.2.0-rc.1 | ||
| # switchyard-server --config benchmark/routing-profiles/tb21-escalation-opus-glm-deepseek.toml --port 4000 | ||
|
|
||
| schema_version = 1 | ||
|
|
||
| [llm_clients.openrouter] | ||
| format = "openai_chat" | ||
| base_url = "https://openrouter.ai/api/v1" | ||
| api_key_env = "OPENROUTER_API_KEY" | ||
|
|
||
| [targets.strong] | ||
| id = "anthropic/claude-opus-4.8" | ||
| llm_client = "openrouter" | ||
|
|
||
| [targets.strong.extra_body.reasoning] | ||
| effort = "high" | ||
|
|
||
| [targets.weak] | ||
| id = "z-ai/glm-5.2" | ||
| llm_client = "openrouter" | ||
|
|
||
| [targets.weak.extra_body.reasoning] | ||
| effort = "high" | ||
|
|
||
| [targets.judge] | ||
| id = "deepseek/deepseek-v4-flash" | ||
| llm_client = "openrouter" | ||
|
|
||
| [targets.judge.extra_body.reasoning] | ||
| enabled = false | ||
|
|
||
| # Every conversation starts on the weak tier. The judge reviews the trajectory each | ||
| # turn, and two consecutive escalate verdicts latch the session onto the strong tier. | ||
| [routes.switchyard] | ||
| id = "switchyard" | ||
| type = "llm_classifier" | ||
| classifier_target = "judge" | ||
| strong_target = "strong" | ||
| weak_target = "weak" | ||
| base_threshold = 0.5 | ||
| escalation = { confirmations = 2, recent_turn_window = 28, window_message_chars = 500 } | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.