Scaling Git’s Garbage Collection

• Git

  285 49,844 10.0 C

  Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.

  

• CocoaPods

  54 14,421 8.3 Ruby

  The Cocoa Dependency Manager.

  

It was an issue with Cocoapods: https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomm...

> If I recall correctly it has to do with the way they cache git.

It was not actually the shallow clone, the shallow clone is fine.

The problem was shallow fetches afterwards, as it made computing the minimum set of changes to fetch much harder for git. Not only that, but they'd hit a git edge case which ended up causing disproportionate CPU usage and converting the shallow clones to near-full clones but very, very inefficiently.

This issue was compounded by the very git-unfriendly layout of the repository: one of the directories had >16000 subdirectories, something Git's tree-processing code apparently was not much tested for, leading to significant inefficiencies.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project