创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

GitHub推出Rubicon智能体化Git架构

AI 总结

GitHub公布面向高并发智能体开发的新一代Git存储架构Rubicon。据公司内部测试,该架构可支持5,000个智能体同时操作同一代码仓库,并处理每秒7,200次推送,同时保持较低读取延迟。该架构目前处于有限私人预览阶段,计划明年初扩大开放范围。

深度见解

Rubicon将Git对象存储、请求处理和引用更新解耦,使代码仓库能够扩展并发智能体负载,同时保留现有Git工作方式。

Last week at GitHub Universe, we announced our new Git storage architecture, capable of handling thousands of writes per second with reads that scale on demand. Through internal testing, we’ve demonstrated the ability to support 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. This new architecture is the foundation for GitHub to support agentic development for hundreds of millions of developers, and we’ve been building it underneath GitHub while it keeps running.

Over the past year, agents changed what a busy repository looks like on GitHub. In our first post in this series, we laid out the two principles behind our next-generation Git storage architecture: minimize coordination, and decouple storage from compute. In our last post, we covered the bridge: moving 99.99999% of repositories into Azure, scoping the write quorum to individual references, and standing up virtual replicas backed by Azure Blob Storage.

We also left off with an observation: very little of a write needs to be ordered. Git objects are immutable and named by their contents, meaning two writers can store them at the same time without agreeing on anything. The part of a push that needs agreement is the reference update, and a reference update is tiny in comparison. Virtual replicas were the first step toward building around that, and the means by which we onboard repositories to the new architecture.

#GitHub#Rubicon#Git#Azure Blob Storage#Ref-CAS#Spokes

原文约 15 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。