Ai4
Standard networks degrade multi-tenant AI cluster performance by treating packets uniformly, but autonomous job-aware routing can double workload completion speeds and expand billable capacity on existing silicon.
AI-assisted summary of ON.AI - Faster Jobs. Same GPUs. More Revenue with OptimalNets — original source. Check the original for full context.
Source published:
Detailed notes
## Background Published on YouTube by Ai4 on August 21, 2026, this presentation features OptimalNets CEO Lior Friedman discussing how network-level job awareness can accelerate AI workloads by 2x to 5x on multi-tenant clusters. The session highlights how infrastructure providers can turn committed GPUs and power into increased billable capacity without adding new hardware or increasing power consumption.
## TL;DR Standard multi-tenant AI clusters suffer from 'job-blind' network switching, which routes packets based on generic averages and forces disparate AI workloads to stall together. OptimalNets introduces ON.AI, an autonomous data path control plane running on top of existing network switches to dynamically optimize fabric parameters based on live workload telemetry. This software-driven approach cuts Job Completion Time (JCT) by 2x to 3x, boosts tokens-per-watt efficiency by 30% to 50%, and unlocks substantial billable capacity for GPU cloud operators. By adapting continuously in software, ON.AI future-proofs multi-year hardware investment cycles against rapidly evolving AI model architectures.
## Atmosphere & style The presentation delivers a crisp, pragmatic, and executive-level technical pitch tailored for infrastructure architects and data center operators. Friedman presents with authoritative clarity, systematically dismantling conventional networking assumptions before laying out a structured, data-backed solution. The tone feels grounded, business-savvy, and engineering-driven, moving logically from structural pain points to clear ROI and deployment pathways.
## Key takeaways - [00:04](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=4s) Traditional network fabrics lack workload context, breaking cohesive AI jobs into disjointed packets and causing all concurrent jobs to crawl at a mediocre pace. - [01:40](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=100s) Multi-tenant GPU clouds cannot use static manual network tuning, forcing them to configure for a generic 'average job' that leaves infrastructure optimized for none. - [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) ON.AI functions as an autonomous, software-defined control plane on existing network hardware, requiring zero additional capex, GPUs, or power draw. - [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) Implementing job-aware network control achieves a 2x to 3x reduction in Job Completion Time (JCT) across AI workloads. - [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) Cluster efficiency increases by 30% to 50% more tokens generated per dollar per watt. - [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) The ON.AI engine operates via a four-stage continuous feedback loop: telemetry collection, traffic analysis, parameter optimization, and cyclic network injection. - [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) A three-phase deployment model—Recommendation, Semi-Autonomous, and Fully Autonomous—allows operators to validate optimizations before granting automated control. - [07:19](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=439s) Data center providers can recapture up to 50% more billable capacity from their committed GPU investments and long-term power agreements. - [07:19](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=439s) ON.AI supports open networking architectures to maximize price-to-performance while avoiding proprietary vendor lock-in. - [07:19](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=439s) Dynamic software adaptation future-proofs physical AI infrastructure, bridging the gap between frequent AI model releases and 3-to-5-year hardware replacement cycles.
## Detailed walkthrough ### [00:04](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=4s) The Challenge of Blind Networks in Multi-Tenant AI Clusters
Traditional networking architectures fundamentally fail to understand the workloads they transport. In standard enterprise and cloud environments, hundreds of employees across diverse departments—from marketing to R&D—as well as autonomous AI agents are constantly submitting disparate AI tasks to shared clusters. Conventional AI infrastructure takes these cohesive workloads, breaks them down into billions of disjointed packets, and routes them across thousands of GPUs. Because standard network hardware treats all packets uniformly, every workload advances at roughly the same mediocre pace, forcing virtually every user to wait longer than necessary for their results.
OptimalNets addresses this structural inefficiency with **ON.AI**, an autonomous data path control plane designed specifically for AI clusters. Rather than allowing all tasks to crawl forward simultaneously and finish in a delayed cluster at the very end, introducing job awareness enables the network to prioritize and complete individual jobs as quickly as possible. This paradigm shift returns actionable results to users earlier, recaptures millions of dollars in idle GPU capacity, and significantly boosts business productivity.
- AI infrastructure natively understands packets rather than complete computational jobs. - Multiplexing unrelated workloads across identical, uncalibrated paths causes broad job latency. - Introducing job awareness ensures workloads complete sequentially and rapidly rather than stalling together.
```mermaid flowchart TD accTitle: Standard Blind Switching vs. Job-Aware ON.AI Data Path accDescription: Comparison showing how traditional networks mix disjointed packets while ON.AI uses a continuous control loop to maintain job awareness.
subgraph Standard["Standard Cluster Networking (Job-Blind)"] direction TB A1["Users & Agents Submit Jobs"] --> B1["Schedulers Distribute to GPUs"] B1 --> C1["Jobs Sliced into Raw Packets"] C1 --> D1["Packets Mixed in Network Fabric<br><i>(Tuned for the 'Average Job')</i>"] D1 --> E1["Uniform Slow Progress & High Latency"] end
subgraph Optimal["OptimalNets ON.AI Control Plane"] direction TB A2["GPU Inter-Connect Telemetry"] --> B2["ON.AI Model Engine<br><i>(Understands Jobs & Network Dynamics)</i>"] B2 --> C2["Dynamic Parameter Optimization"] C2 --> D2["Network Applies Job-Aware Policies"] D2 --> E2["2x–3x Faster Job Completion Time"] end ```
---
[01:40](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=100s) Why Shared GPU Clouds Suffer from the "Average Job" Penalty
In a typical AI data center, workloads originating from disparate teams and agentic pipelines are mapped onto GPU hardware via orchestrators and job schedulers. However, when those GPUs communicate with one another to execute distributed training, fine-tuning, or inference, the underlying interconnect splits the jobs into packets and commingles them across the fabric. In doing so, the network completely loses all context regarding which packet belongs to which job, its operational priority, or its latency sensitivity.
``` +-----------------------------------------------------------------------------+ | Divergence in AI Infrastructure Optimization | +-----------------------------------------------------------------------------+ | Dedicated LLM Provider Clouds | Multi-Tenant GPU Clouds & Neoclouds | +----------------------------------------+-------------------------------------+ | • Single, static, known model workload | • Unpredictable user submissions | | • Hardware manually pre-tuned | • Heterogeneous prompts and agents | | • High utilization for one specific job| • Tuned for the generic "average" | | • Not built for multi-tenant diversity | • Result: "Optimized for none" | +----------------------------------------+-------------------------------------+ ```
While elite foundational LLM providers can manually hard-tune their proprietary networks because they run known, static model architectures, that approach breaks down in multi-tenant environments. Hyperscalers, enterprise on-premise data centers, and emerging neoclouds must serve a fluctuating stream of unknown user prompts, diverse model sizes, and agentic workflows. Because these providers cannot anticipate what workloads will arrive, their networks are statically configured for a generic "average job." As a result, the network is truly "not optimized to none," leading to degraded performance, poor utilization, and prolonged user wait times when submitting prompts.
---
[04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) ON.AI: A Model-Driven Autonomous Data Path Control Plane
ON.AI acts as a software-defined, autonomous data path control plane running on top of existing physical hardware. By activating ON.AI, operators achieve a 2x to 3x reduction in Job Completion Time (JCT) while expanding system output by 30% to 50% more tokens per dollar per watt. Crucially, these efficiency gains require no capital expenditures on new GPUs, additional memory, or specialized switching hardware, while concurrently reducing overall operational power consumption.
```mermaid flowchart LR accTitle: ON.AI Autonomous Control Loop accDescription: Cyclic telemetry analysis and parameter injection loop deployed on top of existing switches.
subgraph Hardware["Existing Infrastructure Fabric"] NET["Physical Switches & GPU Network"] end
subgraph ControlPlane["ON.AI Virtual Control Layer"] T1["1. Continuous Telemetry Collection"] T2["2. ON.AI Engine Traffic Analysis"] T3["3. Job-Aware Parameter Calculation"] T4["4. Cyclic Network Injection"] end
NET --> T1 T1 --> T2 T2 --> T3 T3 --> T4 T4 --> NET ```
The underlying intelligence of ON.AI is a proprietary AI model built and trained from scratch to comprehend three critical dimensions: the characteristics of AI workloads, the mechanics of high-speed network fabrics, and the dynamic interplay between them. The platform operates via an ongoing, four-stage closed loop: 1. **Continuous Telemetry Collection:** Ingests live telemetry directly from the running network fabric. 2. **Engine Traffic Analysis:** Analyzes dynamic traffic requirements against workload profiles using the ON.AI engine. 3. **Parameter Optimization:** Computes tailored network parameters aligned with active job needs. 4. **Cyclic Network Injection:** Continuously pushes dynamic configuration updates back to the network, imbuing standard switches with real-time job awareness.
To accommodate risk-averse IT and infrastructure teams that hesitate to alter configurations on expensive GPU clusters, ON.AI supports a phased, non-disruptive deployment pathway: - **Phase 1 (Recommendation Mode):** The system generates passive optimization recommendations, showing administrators exactly what settings to alter without touching production state. - **Phase 2 (Semi-Autonomous Mode):** Operators review and approve suggested control updates with automated push mechanisms. - **Phase 3 (Fully Autonomous Mode):** The control plane closes the loop independently, executing continuous real-time optimizations to extract peak cluster performance.
---
[07:19](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=439s) Core Value Propositions and Future-Proofing GPU Infrastructure
OptimalNets delivers four fundamental business and technical benefits to data center operators, cloud service providers, and end users:
```mermaid flowchart TD accTitle: OptimalNets Core Value Pillars accDescription: Four key pillars of the ON.AI value proposition for GPU infrastructure operators.
VP1["<b>Up to 50% Higher Billable Capacity</b><br>Denser utilization of committed GPU capex and locked-in power contracts"] VP2["<b>2x Faster Job Completion</b><br>Halves turnaround latency for interactive prompts and agentic workflows"] VP3["<b>Open Networking Support</b><br>Avoids proprietary lock-in for superior cost-to-performance economics"] VP4["<b>Continuous Future-Proofing</b><br>Dynamic adaptation to daily model releases on 3–5 year hardware cycles"]
VP1 --- VP2 VP2 --- VP3 VP3 --- VP4 ```
- **Up to 50% Increase in Billable Capacity:** Infrastructure providers make massive upfront capital investments in GPUs and commit to long-term power purchase agreements. ON.AI allows operators to pack workloads significantly more densely onto their committed power and silicon envelope, translating previously stranded resources into billable revenue. - **Faster End-User Turnaround:** End customers and automated agents experience prompt completion in roughly half the time, directly improving user satisfaction and application responsiveness. - **Support for Open Networking Standards:** The platform is built to support open network fabrics, maximizing price-performance and freeing infrastructure teams from vendor lock-in. - **Resilience Against Model Churn (Future-Proofing):** Modern AI models evolve on a weekly or daily basis, each introducing novel communication patterns and tensor-parallel requirements. Because physical data center hardware undergoes upgrade cycles only once every 3 to 5 years, ON.AI bridges the gap by continuously learning new model behaviors in software, ensuring existing hardware remains optimized for next-generation architectures.
The session concludes with an open invitation for cluster operators and GPU cloud architects to engage directly with the OptimalNets engineering team via LinkedIn, email, or at their conference location (Booth K522).
## Notable quotes > Faster job completion turns your committed GPUs and power into more billable capacity — and happier customers. — Lior Friedman
> 2–5x faster job completion once the network becomes job-aware. That speed costs nothing extra — no new hardware, no new software stack, no new power draw. — Lior Friedman
> [00:04](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=4s) Traditional networking architectures fundamentally fail to understand the workloads they transport. — Lior Friedman
> [00:04](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=4s) Because standard network hardware treats all packets uniformly, every workload advances at roughly the same mediocre pace, forcing virtually every user to wait longer than necessary for their results. — Lior Friedman
> [00:04](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=4s) Introducing job awareness ensures workloads complete sequentially and rapidly rather than stalling together. — Lior Friedman
> [01:40](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=100s) the network completely loses all context regarding which packet belongs to which job, its operational priority, or its latency sensitivity. — Lior Friedman
> [01:40](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=100s) Because these providers cannot anticipate what workloads will arrive, their networks are statically configured for a generic "average job." As a result, the network is truly "not optimized to none" — Lior Friedman
> [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) ON.AI acts as a software-defined, autonomous data path control plane running on top of existing physical hardware. — Lior Friedman
> [04:22](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=262s) 2x to 3x reduction in Job Completion Time (JCT) while expanding system output by 30% to 50% more tokens per dollar per watt. — Lior Friedman
> [07:19](https://www.youtube.com/watch?v=GNi9Hf9nmUo&t=439s) Because physical data center hardware undergoes upgrade cycles only once every 3 to 5 years, ON.AI bridges the gap by continuously learning new model behaviors in software, ensuring existing hardware remains optimized for next-generation architectures. — Lior Friedman
## Mentioned Lior Friedman, OptimalNets, ON.AI, Ai4, LinkedIn
## Video description Lior Friedman - CEO, OptimalNets
Faster job completion turns your committed GPUs and power into more billable capacity — and happier customers. On every multi-tenant, multi-job cluster, unrelated workloads share the same network. Standard infrastructure applies one generic setting to all of them, so every job underutilizes the GPUs and the committed power behind it, and runs slower than it can. I'll show benchmark data across inference, fine-tuning, and training workloads: 2–5x faster job completion once the network becomes job-aware. That speed costs nothing extra — no new hardware, no new software stack, no new power draw. Come by if you run GPU infrastructure, or if you're a customer who wants faster jobs and should be asking your provider for it.
[Source](https://www.youtube.com/watch?v=GNi9Hf9nmUo)