Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#162 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 5 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
go
Bereich
desktop

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Go
Sterne
1.6k
Forks
266
Ø Merge
3 T. 15 Std.
Gemergte PRs (30 T.)
23

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus NVIDIA/Personal-AI-Router

Alle Issues in NVIDIA/Personal-AI-Router

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.