git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Mercurial 0.4e vs git network pull

From
Daniel Barkalow <barkalow@iabervon.org>
Date
May 12, 2005, 21:24 UTC
Message-ID
<Pine.LNX.4.21.0505121709250.30848-100000@iabervon.org>
In-Reply-To
<20050512205735.GE5914@waste.org>
On Thu, 12 May 2005, Matt Mackall wrote:
> 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.

It requires a request per object, but it should be possible (with somewhat more complicated code) to overlap them such that it doesn't require a serial round trip for each. Since the server is sending static files, the overhead for each should be minimal.

> How does git find the outstanding changesets?

In the present mainline, you first have to find the head commit you want. I have a patch which does this for you over the same connection. Starting from that point, it tracks reachability on the receiving end, and requests anything it doesn't have.

For the case of having nothing to do, it should be a single one-line request/response for a static file (after which the local end determines that it has everything it needs without talking to the server).

	-Daniel
*This .sig left intentionally blank*
Previous: Matt MackallNext: Matt Mackall
Message 6 of 14 in “Mercurial 0.4e vs git network pull”
  1. Matt MackallMay 12, 2005
  2. Petr BaudisMay 12, 2005
  3. Matt MackallMay 12, 2005
  4. Petr BaudisMay 12, 2005
  5. Matt MackallMay 12, 2005
  6. Daniel BarkalowMay 12, 2005
  7. Matt MackallMay 12, 2005
  8. Daniel BarkalowMay 13, 2005
  9. Matt MackallMay 13, 2005
  10. Daniel BarkalowMay 13, 2005
  11. Matt MackallMay 13, 2005
  12. Petr BaudisMay 13, 2005
  13. Petr BaudisMay 15, 2005
  14. Ingo MolnarMay 15, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.