From: Junio C Hamano <gitster@pobox.com>
To: Andreas Ericsson <ae@op5.se>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>,
spearce@spearce.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: Is anyone working on a next-gen Git protocol?
Date: Mon, 08 Oct 2012 09:27:04 -0700 [thread overview]
Message-ID: <7vtxu5lyjr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5072973D.4080703@op5.se> (Andreas Ericsson's message of "Mon, 08 Oct 2012 11:05:01 +0200")
Andreas Ericsson <ae@op5.se> writes:
> You'll want that to be a single "wants" message to avoid incurring
> insane amounts of roundtrip latency with lots of refs. github and
> other hosted services are quite popular, but with my 120ms ping
> rtt I'd be spending half a minute just telling the other side what
> I want when I fetch from a repo with 250 refs.
Peff's recent patch when applied on the server side would help
alleviate the load to produce these refs, but it obviously would not
cut the network cost. In order to change this, we need to swap "who
speaks first".
Once we go into "want/have" phase, I do not think there is a need
for fundamental change in the protocol (by this, I am not counting a
change to send "have"s sparsely and possibly backtracking to bisect
history, etc. as "fundamental").
next prev parent reply other threads:[~2012-10-08 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 19:57 Is anyone working on a next-gen Git protocol? Ævar Arnfjörð Bjarmason
2012-10-07 20:22 ` Ilari Liusvaara
2012-10-07 22:08 ` Jeff King
2012-10-07 22:31 ` Junio C Hamano
2012-10-22 4:59 ` Junio C Hamano
2012-10-08 9:05 ` Andreas Ericsson
2012-10-08 16:27 ` Junio C Hamano [this message]
2012-10-10 19:13 ` Steffen Prohaska
2012-10-10 20:46 ` Junio C Hamano
2012-10-10 22:32 ` Philip Oakley
2012-10-11 1:44 ` Nguyen Thai Ngoc Duy
2012-10-11 3:08 ` Shawn Pearce
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtxu5lyjr.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).