From: Jeff Garzik <jgarzik@pobox.com>
To: Matt Mackall <mpm@selenic.com>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
pasky@ucw.cz, git@vger.kernel.org, linux-kernel@vger.kernel.org,
mercurial@selenic.com, torvalds@osdl.org
Subject: Re: Mercurial 0.4e vs git network pull
Date: Sun, 15 May 2005 14:23:29 -0400 [thread overview]
Message-ID: <428793A1.5070004@pobox.com> (raw)
In-Reply-To: <20050515173923.GK5914@waste.org>
Matt Mackall wrote:
> On Sun, May 15, 2005 at 04:22:19AM -0700, Adam J. Richter wrote:
>
>>On Sun, 15 May 2005 10:54:05 +0200, Petr Baudis wrote:
>>
>>>Dear diary, on Thu, May 12, 2005 at 10:57:35PM CEST, I got a letter
>>>where Matt Mackall <mpm@selenic.com> told me that...
>>>
>>>>Does this need an HTTP request (and round trip) per object? It appears
>>>>to. That's 2200 requests/round trips for my 800 patch benchmark.
>>
>>>Yes it does. On the other side, it needs no server-side CGI. But I guess
>>>it should be pretty easy to write some kind of server-side CGI streamer,
>>>and it would then easily take just a single HTTP request (telling the
>>>server the commit ID and receiving back all the objects).
>>
>> I don't understand what was wrong with Jeff Garzik's previous
>>suggestion of using http/1.1 pipelining to coalesce the round trips.
>
>
> You can't do pipelining if you can't look ahead far enough to fill the pipe.
Even if you cannot fill a pipeline, HTTP/1.1 is sufficiently useful
simply by removing the per-request connection overhead.
Jeff
next prev parent reply other threads:[~2005-05-15 18:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 11:22 Mercurial 0.4e vs git network pull Adam J. Richter
2005-05-15 12:40 ` Petr Baudis
2005-05-16 22:22 ` Tristan Wibberley
2005-05-16 22:22 ` Tristan Wibberley
2005-05-15 17:39 ` Matt Mackall
2005-05-15 18:23 ` Jeff Garzik [this message]
2005-05-16 1:12 ` Matt Mackall
2005-05-16 9:29 ` Matthias Urlichs
2005-05-16 9:29 ` Matthias Urlichs
-- strict thread matches above, loose matches on Subject: below --
2005-05-15 11:52 Adam J. Richter
2005-05-15 14:23 ` Petr Baudis
2005-05-12 9:44 Matt Mackall
2005-05-12 18:23 ` Petr Baudis
2005-05-12 20:11 ` Matt Mackall
2005-05-12 20:14 ` Petr Baudis
2005-05-12 20:57 ` Matt Mackall
2005-05-12 21:24 ` Daniel Barkalow
2005-05-12 22:29 ` Matt Mackall
2005-05-13 0:33 ` Daniel Barkalow
2005-05-13 1:11 ` Matt Mackall
2005-05-13 2:23 ` Daniel Barkalow
2005-05-13 2:44 ` Matt Mackall
2005-05-13 5:44 ` Petr Baudis
2005-05-15 8:54 ` Petr Baudis
2005-05-15 0:40 ` Christian Kujau
2005-05-15 8:50 ` Petr Baudis
2005-05-15 15:12 ` Christian Kujau
2005-05-15 6:22 ` Ingo Molnar
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=428793A1.5070004@pobox.com \
--to=jgarzik@pobox.com \
--cc=adam@yggdrasil.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=mpm@selenic.com \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.