Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature]: PAIR feedback: model-level routing toggles, controlled test runs, and concurrency controls

Abierto
  • ¿Algo no está bien?
#162 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
desktop

Línea de trabajo

This is a broad feature request covering several separate controls: per-model routing toggles, keep-loaded, concurrency limits, and test-runner scope. No files, tests or entry points are named in the payload, so start by locating the model load/eject actions and the test runner in the desktop UI. Done would mean the request is split into smaller issues with agreed scope.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement
Area

Desktop experience

User problem

Hi NVIDIA PAIR team,

First, thank you for building and releasing Personal AI Router. I’m genuinely excited about the product. I love NVIDIA’s local AI direction, and PAIR is exactly the kind of tool I want to use across my RTX machines.

After setting up PAIR across two Windows systems, I ran into a few workflow issues that I think could be improved with some model-level controls.

Right now, PAIR appears to expose model actions like load and eject, but I could not find a clean way to decide which installed models are eligible for routing. That makes the routing behavior feel too automatic. I would love to see controls such as:

  • Enable/disable routing per model
  • Keep-loaded toggle per model
  • Max concurrent models per node
  • Preferred node per model
  • “Test selected model only”
  • “Test selected node only”
  • A safer “test all” mode that runs one model at a time, or with a visible concurrency limit
  • Time Based Scheduled Loading of Model or Models and Model Grouping

In my setup, the broad test behavior appeared to launch many workload checks across many models at once. Some tests passed, but many failed with messages like “client disconnected before completion” or “context canceled.” When I tested specific models one at a time, the routes worked much more reliably. So the issue seemed less like every model was broken and more like the test runner was overloading the environment or timing out before queued model loads could complete.

I think PAIR would be much easier to trust if installed models, loaded models, and routing-eligible models were treated as separate states in the UI.

Thank you again for the work on PAIR. I’m excited about where this is going, and I hope this feedback is useful.

Best,
Chris

Desired outcome
  • Enable/disable routing per model
  • Keep-loaded toggle per model
  • Max concurrent models per node
  • Preferred node per model
  • “Test selected model only”
  • “Test selected node only”
  • A safer “test all” mode that runs one model at a time, or with a visible concurrency limit
  • Time Based Scheduled Loading of Model or Models and Model Grouping
Alternatives considered

No response

Compatibility and security implications

No response

Validation approach

No response

Confirmations
  • I searched existing issues for duplicates.
  • I agree to follow the Code of Conduct.
Lenguaje dominante
Go
Estrellas
1.6k
Forks
277
Merge medio
4 d 14 h
PR fusionados (30 d)
31

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NVIDIA/Personal-AI-Router

Todos los issues de NVIDIA/Personal-AI-Router

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.