Skip to content

Add Dragonfly to I/O bottlenecks in AI Scheduling Challenges whitepaper - #2272

Open
pmady wants to merge 1 commit into
cncf:mainfrom
pmady:dragonfly-io-bottlenecks
Open

Add Dragonfly to I/O bottlenecks in AI Scheduling Challenges whitepaper#2272
pmady wants to merge 1 commit into
cncf:mainfrom
pmady:dragonfly-io-bottlenecks

Conversation

@pmady

@pmady pmady commented Aug 10, 2026

Copy link
Copy Markdown

Follow-up to #2164. Marlow asked me to send this straight to cncf/toc.

Ch 4, I/O Bottlenecks: the "Model loading for inference" list has an empty bullet right after "Cold start" looks like a placeholder that shipped blank. Filled it with the scale-out case: when a lot of replicas start at once they each pull the same weights independently and hammer the registry. The streaming tools in the cold start bullet help per-pod latency but don't do anything for that.

Ch 5: added Dragonfly (CNCF graduated) to Data and Storage Tools and to the I/O Bottlenecks row of the mapping table. Alphabetical in both, to match what's already there.

Happy to reword or make any changes.

…a tools

Chapter 4 had an empty placeholder bullet under "Model loading for
inference", following the existing "Cold start" entry. Fill it with the
distribution-at-scale case: many replicas starting together each pull the
same weights independently, saturating registry egress. Cold-start
streaming tools address per-pod latency but not this aggregate load.

Chapter 5 adds Dragonfly to Data and Storage Tools and to the I/O
Bottlenecks row of the challenge-to-solution mapping table. Both are
ordered alphabetically, consistent with the rest of the section.

Dragonfly is a CNCF Graduated project for peer-to-peer distribution of
container images and AI model artifacts.

Signed-off-by: Pavan Madduri <pavan4devops@gmail.com>
@pmady
pmady requested review from a team as code owners August 10, 2026 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant