-
Notifications
You must be signed in to change notification settings - Fork 601
feature: Model onboarding procedure #1153
Copy link
Copy link
Open
Labels
area/model-selectionModel selection algorithms and routingModel selection algorithms and routingarea/momMixture of Models (MoM) enhancementsMixture of Models (MoM) enhancementsenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededpriority/P1Important / Should-HaveImportant / Should-Haveroadmap
Milestone
Description
Describe the feature
Right now, the router config uses model endpoint, and assigns signals, without a transparent and consistent way of evaluating the model or routing policy.
Why do you need this feature?
We need an model onboard procedure that does the following:
- Evaluate the model through curated benchmark to infer the latency, accuracy, reasoning, and token consumption.
- Update the config if necessary especially if the model's eval results are not covered by the (e.g. accuracy, latency) thresholds used by signals
- Update routing models, e.g. the embedding based clustering.
- Update the config and continuously monitor the new model's performance through online learning feature: enhance online learning with bidirectional signal extraction #1140
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/model-selectionModel selection algorithms and routingModel selection algorithms and routingarea/momMixture of Models (MoM) enhancementsMixture of Models (MoM) enhancementsenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededpriority/P1Important / Should-HaveImportant / Should-Haveroadmap
Type
Projects
Status
In progress