All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Julian Phillips" <jp3@quantumfyre.co.uk>
Cc: git@vger.kernel.org
Subject: Re: [PU PATCH] Fix git fetch for very large ref counts
Date: Mon, 12 Feb 2007 19:18:07 -0800	[thread overview]
Message-ID: <7vd54e4ufk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11713297014015-git-send-email-julian@quantumfyre.co.uk> (Julian Phillips's message of "Tue, 13 Feb 2007 01:21:38 +0000")

"Julian Phillips" <jp3@quantumfyre.co.uk> writes:

> The updated git fetch in pu is vastly improved on repositories with very
> large numbers of refs.  The time taken for a no-op fetch over ~9000 refs
> drops from ~48m to ~0.5m.
>
> However, before git fetch will actually run on a repository with ~9000
> refs the calling interface between fetch and fetch--tool needs to be
> changed.  The existing version passes the entire reflist on the command
> line, which means that it is subject to the maxiumum environment size
> passed to a child process by execve.
>
> The following patches add a stdin based interface to fetch--tool allowing
> the ~9000 refs to be passed without exceeding the environment limit.

Thanks.

But the ones in 'pu' were done primarily as demonstration of
where the bottlenecks are, and not meant for real-world
consumption.  I think the final shaving of 0.5m down to a few
seconds needs to move the ls_remote_result string currently kept
as a shell variable to a list of strings represented in a
git-fetch largely rewritten in C, and at that point the
interface from outside fetch--tool to throw 9000 refs at it
would be an internal function call and the code you fixed along
with new function you introduced would probably need to be
discarded.

  parent reply	other threads:[~2007-02-13  3:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13  1:21 [PU PATCH] Fix git fetch for very large ref counts Julian Phillips
2007-02-13  1:21 ` [PATCH] Allow fetch--tool to read from stdin Julian Phillips
2007-02-13  1:21   ` [PATCH] Use stdin reflist passing in parse-remote Julian Phillips
2007-02-13  1:21     ` [PATCH] Use stdin reflist passing in git-fetch.sh Julian Phillips
2007-02-13  2:31       ` Linus Torvalds
2007-02-13  3:18 ` Junio C Hamano [this message]
2007-02-13 10:39   ` [PU PATCH] Fix git fetch for very large ref counts Julian Phillips
2007-02-13 17:58     ` Junio C Hamano

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=7vd54e4ufk.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jp3@quantumfyre.co.uk \
    /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.