惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园_首页
B
Blog RSS Feed
Microsoft Azure Blog
Microsoft Azure Blog
J
Java Code Geeks
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Google DeepMind News
Google DeepMind News
F
Fortinet All Blogs
V
V2EX
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Engineering at Meta
Engineering at Meta
月光博客
月光博客
阮一峰的网络日志
阮一峰的网络日志
M
MIT News - Artificial intelligence
IT之家
IT之家
博客园 - 【当耐特】
U
Unit 42
云风的 BLOG
云风的 BLOG
L
LangChain Blog
小众软件
小众软件
Microsoft Security Blog
Microsoft Security Blog
B
Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
宝玉的分享
宝玉的分享
N
Netflix TechBlog - Medium

InfoQ

GitHub Copilot Open-Source Project Brings Full iOS 27 Virtualization to Apple Silicon From Retrieval to Reasoning: Building Production-Ready Agentic AI Systems with Knowledge Graphs Lambda SnapStart Comes to Container Images, Ending a Packaging Tradeoff One Decade of Rustls: Evolution, Benchmarks, and Future Roadmap Netflix Reworks Conductor for 420 Million Monthly Workflow Executions and 10X Larger Workflows tsgolint Reaches Stable v7, Bringing Go-Powered Type-Aware Linting to Oxlint Terraform AWS Provider Continues Rapid Expansion as AWS Infrastructure Becomes More Complex How To Run on Three Clouds at Once, and When Not To How LinkedIn Trains AI Job Search 8x Faster with Multi-Teacher Distillation Session Traces and Cost Controls Help Diagnose AI Agent Failures Advancing Embedded Go: Recoverable Panics, UEFI, Radio and Hardware Dev Kit Blume: Zero-Config Docs Framework That Turns a Markdown Folder into an AI-Ready Website Redefining GIS: Declarative Symbology and Collaborative Workflows in JupyterGIS Airbnb Cuts Authentication Code by 60% with Server Driven Architecture Kubernetes Promotes KYAML as a Safer, More Consistent Way to Work with Manifests Next-Gen Architecture Playbook: Insights and Patterns for the AI Era From S3 to GPU in One Copy: Rethinking Data Loading for ML Training Copilot Code Review Reaches Azure Repos, Billed Per Review with Reporting Two Days Behind Personality Over Skillset: How Adam Wachtel Builds Engineering Teams Tether: Apple Continuity Like Experience Between iOS and Linux Desktop Machines Twenty Years of jQuery: How a Little Library Rewired Web Development Shopify Introduces Gisting: Compressing LLM System Prompts into Learned Tokens Rigorous Yet Sustainable Human Reviews in the AI Era pnpm 12 Rewrites Package Manager in Rust, Accelerating Installs While Preserving pnpm 11 Workflows Instrumentation at Scale: Having Your Performance Cake and Eating It Too Cohere’s Parse 5 Promises Efficient Multi-Modal Information Extraction From Complex Documents Swiggy Uses 350+ Features and Multi-Task MLP to Predict Customer Lifetime Value OpenAI Details GPT-Live’s Architecture for Continuous Stateful Voice Interaction Beyond Prompting: Context Engineering for Production-Grade AI
NVIDIA Personal AI Router Distributes AI Tasks across Loc...
Sergio De Simone · 2026-09-11 · via InfoQ

NVIDIA Personal AI Router (PAIR), now available in beta, lets you combine the inference capacity of multiple computers on your local network and automatically distribute AI requests among them. It is primarily designed for local multi-agent AI workloads, where multiple independent model calls can otherwise overwhelm one GPU.

NVIDIA says a breadth-first approach to distributing agentic tasks is becoming increasingly common, with a lead agent dispatching subtasks to sub-agents or multiple agents working together to complete more complex tasks. However, this approach can create a bottleneck on the local GPU when it receives too many requests.

To address this challenge, NVIDIA PAIR maximizes the AI compute available locally by distributing individual inference requests across available systems. It integrates seamlessly with popular local inference services such as Ollama and LM Studio without requiring changes to the underlying architecture or agent harness.

Agents can send a request through the familiar local interface it expects. PAIR receives the request through its proxy, identifies its engine and model requirements, and selects one eligible node. That node executes the request from start to finish and sends the response back through PAIR. The agent continues to see one connection while PAIR handles placement behind it.

To demonstrate PAIR’s capabilities, NVIDIA released a demo combining Hermes Desktop, Ollama, and PAIR showing roughly a 2x reduction in completion time when combining an RTX Spark, a DGX Spark, and an RTX 5090 via PAIR compared with running the workload on a single RTX Spark laptop. In the demo, Hermes breaks the task into five independent specialist analyses, delegates them, reconciles their findings, and synthesizes the final plan—covering what needs to happen tonight, this week, later, or not at all. PAIR handles the distribution of these inference requests across available nodes, while Ollama runs the model on whichever node PAIR selects. NVIDIA notes, however, that the demo should not be taken as a performance guarantee, as results depend on multiple factors including workload parallelism, model, engine settings, hardware, network, and node availability.

NVIDIA PAIR can be used on Windows 11, Linux, and macOS, with support for both x64 and arm64 systems. It can also pair nodes running different operating systems, dispatching a task to a given node only if the required model or engine is known to be compatible with that node. NVIDIA explicitly notes that PAIR does not "merge GPUs or pool VRAM into one larger accelerator". Instead, it distributes individual inference requests across available systems.

Despite these disclaimers, NVIDIA's announcement sparked some confusion on social media, with users interpreting PAIR as a solution for sharing their available compute with third-parties or for running complex models by combining less capable compute.

Reddit user Vegetable-Warthog81 described their positive experience with PAIR using it to distribute inference across three RTX 5090s running Qwen 3.8 27B using Ollama:

PAIR makes distributing jobs across the three machines pretty painless. For long, repetitive “grunt work” where I care more about stability and just keeping all the GPUs busy than squeezing out maximum tokens/sec, it’s been surprisingly nice.

PAIR can be downloaded from GitHub. For a step-by-step introduction to how to use it, see the Getting Started documentation.

If you are looking for a platform that enables GPU compute to be shared across a network of parties, check Petals or Mesh LLM. Mesh LLM also supports splitting models that are too large to fit on a single machine using Skippy.

About the Author

Sergio De Simone