Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262130AbVELV1M (ORCPT ); Thu, 12 May 2005 17:27:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262132AbVELV0y (ORCPT ); Thu, 12 May 2005 17:26:54 -0400 Received: from iabervon.org ([66.92.72.58]:43013 "EHLO iabervon.org") by vger.kernel.org with ESMTP id S262130AbVELVYy (ORCPT ); Thu, 12 May 2005 17:24:54 -0400 Date: Thu, 12 May 2005 17:24:27 -0400 (EDT) From: Daniel Barkalow To: Matt Mackall cc: Petr Baudis , linux-kernel , git@vger.kernel.org, mercurial@selenic.com, Linus Torvalds Subject: Re: Mercurial 0.4e vs git network pull In-Reply-To: <20050512205735.GE5914@waste.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1237 Lines: 29 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* - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/