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

Re: Git-status / preload_index() performance

From
David Turner <dturner@twopensource.com>
Date
Jun 24, 2014, 23:12 UTC
Message-ID
<1403651538.22828.4.camel@stross>
In-Reply-To
<53AA0129.1080109@gmail.com>
On Wed, 2014-06-25 at 00:52 +0200, Karsten Blees wrote:
> Even more time is spent unpacking the HEAD tree, even with hot cache (repacking with depth 10 reduces this to ~250ms, on SSD its just 7ms). Perhaps caching the HEAD tree in an index extension could help here?

This is approximately what the cache-tree extension does. However, it's a bit broken. I've been working on a fix, but slowly because my other work has taken me longer than expected. You can see the effect of the cache-tree extension by doing git reset --hard HEAD; this temporarily restores that extension.

Previous: Duy NguyenNext: Karsten Blees
Message 8 of 9 in “Git-status / preload_index() performance”
  1. Karsten BleesJun 24, 2014
  2. preload-index: optimize for sequential IOKarsten Blees, Jun 24, 2014
  3. preload-index: make parallel IO configurableKarsten Blees, Jun 24, 2014
  4. test git-status performanceKarsten Blees, Jun 24, 2014
  5. Duy NguyenJun 26, 2014
  6. Duy NguyenJul 26, 2014
  7. Duy NguyenJul 26, 2014
  8. David TurnerJun 24, 2014
  9. Karsten BleesJun 24, 2014

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.