Towards An Application Objective-Aware Network Interface
summary
Cloud network interface proposes CadentFlow as an ANI with per-flow priorities or deadlines and an explicit application objective, implemented for parameter‑server distributed deep learning and compared to TCP and coflow. Experiments with 8 workers and 8 parameter servers show up to 25% improvement in iteration time, while 16×16 setups show smaller gains because computation becomes the bottleneck. The paper also defines CCT flexibility ratio to quantify how much bandwidth scheduling can be delayed.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:28Evolution of Application Network Interface 4
- 2:27What is the ultimate goal of an ANI?
- 2:48Understanding an Application's Objective
- 5:03An Example Application: Distributed Deep Lea
- 6:39Other Applications
- 8:11Towards A Novel Application Network Inter
- 9:40Defining CCT flexibility ratio
- 11:53Distributed DNN Training CadentFlow
- 15:00Quantifying benefits achievable with a better network a
- 16:21Performance Improvement
- 18:30Open Challenges
related talks
14mBrain-on-Switch: Towards Advanced Intelligent Network Data Plane via NN-Driven Traffic...
13mContracting Wide-area Network Topologies to Solve Flow Problems Quickly
16mBackpressure Flow Control
26mEvolution of Application Visibility for Telcos: From Programmable Switches to Cloud Native
17mPerformance Interfaces for Network Functions
21mYour Coflow has Many Flows: Sampling them for Fun and Speed
16mFlow Scheduling with Imprecise Knowledge
31mFlow-based Packet Processing Framework on DPDK and VPP
