On Tue, Jan 31, 2017 at 01:48:05AM +0100, Jeff King wrote: > The list of topics is totally open. If you're coming and have something > you'd like to present or discuss, then propose it here. If you're _not_ > coming, you may still chime in with input on topics, but please don't > suggest a topic unless somebody who is there will agree to lead the > discussion. I would like to talk about the possibility of CDN-aided cloning operations as mentioned on this list earlier this week: http://public-inbox.org/git/CADoxLGPFgF7W4XJzt0X+xFJDoN6RmfFGx_96MO9GPSSOjDK0EQ@xxxxxxxxxxxxxx/ At Bitbucket we have recently rolled out so-called clonebundle support for Mercurial repositories. Full clone operations are rather expensive on the server and are responsible for a substantial part of our CPU and IO load. CDN-based clonebundles have allowed us to eliminate most of this load for Mercurial repos and we've since built a clonebundle spike for Git. Clients performing a full clone get redirected to a CDN where they seed their new local repo from a pre-built bundle file, and then pull/fetch any remaining changes. Mercurial has had native, built-in support for this for a while now. I imagine other large code hosts could benefit from this as well and I'd love to gauge the group's interest for this. Could this make sense for Git? Would it have a chance of landing? Our spike implements it as an optional capability during ref advertisement. What are your thoughts on this? Cheers, Erik