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

Re: [RFC/PATCH 0/3] Teach builtin-clone to pack refs

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 23, 2008, 00:45 UTC
Message-ID
<7v8x0agtdn.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200803220210.30957.johan@herland.net>
Johan Herland <johan@herland.net> writes:
Show 5 quoted lines
> Although most of the speedup from current "next" is achieved by the
> builtin-clone work, there is still a considerable additional improvement
> from writing all refs to a single file instead of writing one file per
> ref. I expect the performance improvement to be much bigger on platforms
> with slower filesystem (aka. Windows).
At some point, additional speedups are hidden in the noise.

Not writing reflogs is a _different_ behaviour from the previous, but I suspect it might even be an improvement. When you have 1000 remote branches, probably most of them are not even active.

Previous: Daniel BarkalowNext: Johan Herland
Message 12 of 13 in “Teach builtin-clone to pack refs”
  1. 0/3 Teach builtin-clone to pack refsJohan Herland, Mar 22, 2008
  2. 1/3 Move pack_refs() and friends into libgitJohan Herland, Mar 22, 2008
  3. 2/3 Prepare testsuite for a "git clone" that packs refsJohan Herland, Mar 22, 2008
  4. Daniel BarkalowApr 14, 2008
  5. Johan HerlandApr 14, 2008
  6. 1/4 Incorporate fetched packs in future object traversalJohan Herland, Apr 14, 2008
  7. 2/4 Move pack_refs() and friends into libgitJohan Herland, Apr 14, 2008
  8. 3/4 Prepare testsuite for a "git clone" that packs refsJohan Herland, Apr 14, 2008
  9. 4/4 Teach "git clone" to pack refsJohan Herland, Apr 14, 2008
  10. 3/3 Teach "git clone" to pack refsJohan Herland, Mar 22, 2008
  11. Daniel BarkalowMar 22, 2008
  12. Junio C HamanoMar 23, 2008
  13. Johan HerlandMar 23, 2008

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.