馃摝 Improve native Git storage of large binary files
<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Problem to solve Git servers perform best with high performance storage, but storing large binary files on high performance storage mediums like SSDs is expensive. If I was previously using Git LFS for large binary files, I could offload these to cheaper storage like object storage. ## Further details The transport protocol for large files might also be improved with support for simple resumable HTTP GET requests. These are easily cacheable, possibly allowing better distributed architectures for remote teams and CI build farms. ## Proposal There should be a way to store large binary files on a cheaper storage tier to the main repository In support of this we are working on: - Supporting a dumb HTTP driver for promisors is helpful for offloading large objects to object storage https://gitlab.com/gitlab-org/git/issues/2 ~"git contribution" We may be able to expose this internally, so that large binary files can be offloaded transparently. Additionally, it may be possible to expose the dumb HTTP interface through GitLab workhorse, to provide resumable HTTP GET access to large binary objects.
epic