Towards Efficient HPC Systems for Agents: Challenges and Opportunities

A September 30, 2026 arXiv paper measuring coding-agent use of high-performance computing systems found that users running coding agents were only 19.5% of the observed population yet generated 55.8% of job submissions, 29.1% of CPU core-hours, and 42.7% of GPU-hours. The authors report agents issue commands at 20.8x the human rate and decompose work into fine-grained explore-modify-execute loops, straining schedulers, bandwidth-provisioned filesystems, and creating new prompt-injection and policy-enforcement surfaces. The paper argues HPC facilities should treat agents as first-class principals and co-design compute, storage, agent memory, and safety rather than banning agents or treating them as ordinary users.

Computer Science Distributed, Parallel, and Cluster Computing Submitted on 30 Sep 2026 Title:Towards Efficient HPC Systems for Agents: Challenges and Opportunities View PDF https://arxiv.org/pdf/2609.38723 HTML experimental https://arxiv.org/html/2609.38723v1 Abstract:Coding agents have become real users of high-performance computing HPC systems, yet today's HPC abstractions, interfaces, and policies remain designed for human-driven workflows. In our measurement, users running coding agents are only 19.5% of the observed population, but account for 55.8% of job submissions, 29.1% of CPU core-hours, and 42.7% of GPU-hours. Agents are not simply faster humans. They issue commands at 20.8x the human rate, decompose work into fine-grained explore-modify-execute loops, and pursue open-ended goals through trial-and-error campaigns that continue through nights and weekends. These behaviors strain abstractions built for human timescales, surfacing as control-plane pressure on the scheduler, metadata-intensive I/O on bandwidth-provisioned filesystems, repeated rediscovery of what earlier sessions already learned, and new prompt-injection and policy-enforcement surfaces. Neither banning agents nor treating them as ordinary users is sustainable. We instead argue for co-design, that facilities should treat agents as first-class principals where agents become facility-aware tenants. We outline the resulting challenges and opportunities in compute, storage, agent memory, and safety. References & Citations Loading... Bibliographic and Citation Tools Bibliographic Explorer What is the Explorer? https://info.arxiv.org/labs/showcase.html arxiv-bibliographic-explorer Connected Papers What is Connected Papers? https://www.connectedpapers.com/about Litmaps What is Litmaps? https://www.litmaps.co/ scite Smart Citations What are Smart Citations? https://www.scite.ai/ Code, Data and Media Associated with this Article alphaXiv What is alphaXiv? https://alphaxiv.org/ CatalyzeX Code Finder for Papers What is CatalyzeX? https://www.catalyzex.com DagsHub What is DagsHub? https://dagshub.com/ Gotit.pub What is GotitPub? http://gotit.pub/faq Hugging Face What is Huggingface? https://huggingface.co/huggingface ScienceCast What is ScienceCast? https://sciencecast.org/welcome Demos Recommenders and Search Tools Influence Flower What are Influence Flowers? https://influencemap.cmlab.dev/ CORE Recommender What is CORE? https://core.ac.uk/services/recommender arXivLabs: experimental projects with community collaborators arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website. Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them. Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs https://info.arxiv.org/labs/index.html .