From: Erik van Zijst <erik.van.zijst@gmail.com>
To: peff@peff.net
Cc: git@vger.kernel.org, ssaasen@atlassian.com, mheemskerk@atlassian.com
Subject: Re: [ANNOUNCE] Git Merge Contributor Summit topic planning
Date: Wed, 1 Feb 2017 10:32:12 +0100 [thread overview]
Message-ID: <1485941532-47993-1-git-send-email-erik.van.zijst@gmail.com> (raw)
In-Reply-To: <20170131004804.p5sule4rh2xrgtwe@sigill.intra.peff.net>
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@mail.gmail.com/
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
next prev parent reply other threads:[~2017-02-01 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 0:48 [ANNOUNCE] Git Merge Contributor Summit topic planning Jeff King
2017-01-31 0:59 ` Jeff King
2017-02-01 19:51 ` Christian Couder
2017-02-01 9:32 ` Erik van Zijst [this message]
2017-02-01 14:53 ` Jeff King
2017-02-01 18:06 ` Junio C Hamano
2017-02-01 21:28 ` Jeff King
2017-02-01 21:35 ` Junio C Hamano
2017-02-01 20:37 ` Stefan Beller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1485941532-47993-1-git-send-email-erik.van.zijst@gmail.com \
--to=erik.van.zijst@gmail.com \
--cc=git@vger.kernel.org \
--cc=mheemskerk@atlassian.com \
--cc=peff@peff.net \
--cc=ssaasen@atlassian.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).