Why Git is hard to put on object storage, where write-ahead logs fall short, and how Enroute reaches 7,600+ pushes per second on a single repository.
How we built Git storage for millions of Netlify projects
A technical look at how Netlify built Netlify Source: durable Git storage on S3, scalable caching, push consistency, and support for millions of projects.
Launching S3 Files, making S3 buckets accessible as file systems | Amazon Web Services
Amazon S3 Files makes S3 buckets accessible as high-performance file systems on AWS compute resources, eliminating the tradeoff between object storage benefits and interactive file capabilities while enabling seamless data sharing with ~1ms latencies.
High Performance Git
High Performance Git by Ted Nyman, a book about Git internals and large Git repositories.
S3 is files, but not a filesystem
"Deep" modules, mismatched interfaces - and why SAP is so painful
Gregory Szorc's Digital Home | High-level Problems with Git and How to Fix Them
When Git first came onto the scene in the mid 2000's, I was initially skeptical because of its horrible user interface. But once I learned it, I appreciated its speed and features - especially the ease at which you could create feature branches, merge, and even create commits offline (which was a big deal in the era when Subversion was the dominant version control tool in open source and you needed to speak with a server in order to commit code). When I started using Git day-to-day, it was such an obvious improvement over what I was using before (mainly Subversion and even CVS).
Git at any scale · Cursor
Hosting Git repositories at scale is a nightmare. When Linus Torvalds designed the first version of the information manager from hell (that's actually the tagline for Git, look it up), he had a very specific use case in mind: his own. He wanted to replace BitKeeper, the distributed version control system that was being used to develop the Linux Kernel. Of course, the replacement had to be distributed too. The Kernel is an unusual software project; it is extremely decentralized, with many different maintainers for its many different subsystems. A distributed version control system is a natural fit for this workflow.
Taming a 486MB Git Repo
How I diagnosed and fixed a 486MB git repo where the actual code was only 6MB. Finding bloat, rewriting history, and choosing between Git LFS and compression.
Artifacts: versioned storage that speaks Git
Give your agents, developers, and automations a home for code and data. We’ve just launched Artifacts: Git-compatible versioned storage built for agents. Create tens of millions of repos, fork from any remote, and hand off a URL to any Git client.
git fetch する度に"Auto packing the repository in background for optimum performance." が出る - Qiita
1年ぐらい毎日コミットし続けているディレクトリの話 Auto packing the repository in background for optimum performance. See "git help gc" for manual housekeeping. ...
Introducing git-wt: Worktrees Simplified
In my previous post, I explained why the bare repo pattern makes git worktrees actually pleasant to use. But setting it up manually requires 10+ commands. And t...
Solving Git's Pain Points with Jujutsu (with Martin von Zweigbergk)
Git 3.0's upcoming SHA-256 default will be a costly mistake
Git 3.0 will make SHA-256 the new default content hashing algorithm and it will be an incomprehensibly expensive and ultimately valueless and avoidable global nightmare.
