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

Re: Scalable reference handling

From
MFMartin Fick <mfick@codeaurora.org>
Date
Oct 7, 2011, 18:51 UTC
Message-ID
<201110071251.44052.mfick@codeaurora.org>
In-Reply-To
<4E8F2012.90108@alum.mit.edu>

On Friday, October 07, 2011 09:51:46 am Michael Haggerty wrote:

> I can't write more now, but Martin, if you have time to
> benchmark 9944c7faf903a95d4ed9de284ace32debe21cdc1
> against your repository, I would be very interested to
> learn the results.

The fetch no longer seems to suffer from the large regression, it is now faster (~7m) than 1.7.7 (which was +15m).

As a quick note, if I comment out the invalidate_cached_refs() call in write_ref_sha1() on line 2065 (on top of 9944c7), it is still much faster, only ~2m. Perhaps growing the array on the fly with many refs is still be too inefficient?

-Martin
-- 
Employee of Qualcomm Innovation Center, Inc. which is a 
member of Code Aurora Forum
Previous: Michael Haggerty
Message 8 of 8 in “66 patches and counting”
  1. Michael HaggertyOct 5, 2011
  2. Junio C HamanoOct 5, 2011
  3. Jonathan NiederOct 5, 2011
  4. Martin FickOct 6, 2011
  5. Martin FickOct 7, 2011
  6. Michael HaggertyOct 7, 2011
  7. Scalable reference handlingMichael Haggerty, Oct 7, 2011
  8. Martin FickOct 7, 2011

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.