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

Re: Inexplicably deteriorating performance of Git repositories on Windows

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Nov 23, 2010, 21:13 UTC
Message-ID
<AANLkTik2+e+9M73RdPT5xha0=QGxD1cVfmLih=bDtCTU@mail.gmail.com>
In-Reply-To
<AANLkTimTh7ka21inpovM=qqdWs6j2OcPXVsFh_CMiZ7N@mail.gmail.com>
On Tue, Nov 23, 2010 at 2:08 PM, Dun Peal <dunpealer@gmail.com> wrote:
> However, after a reboot (of all things), `git status` latency
> skyrockets to 14-15s, making the repo unusable.

A reboot clears your cache. Reboot and time the first and second run of git status.

The first one should be slow (due to cold cache), the second one should be roughly as fast as right after a clone.

If it's not, more debugging may be neeed. But always take your timings on a well seeded ('hot') cache.

cheers,
m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
Previous: Dun PealNext: Dun Peal
Message 13 of 21 in “Inexplicably deteriorating performance of Git repositories on Windows”
  1. Dun PealNov 23, 2010
  2. Wilbert van DolleweerdNov 23, 2010
  3. Dun PealNov 23, 2010
  4. Wilbert van DolleweerdNov 23, 2010
  5. Stephen BashNov 23, 2010
  6. Dun PealNov 23, 2010
  7. Tay Ray ChuanNov 24, 2010
  8. Joshua JensenNov 24, 2010
  9. Dun PealNov 24, 2010
  10. A Large Angry SCMNov 24, 2010
  11. Johannes SixtNov 24, 2010
  12. Dun PealNov 24, 2010
  13. Martin LanghoffNov 23, 2010
  14. Dun PealNov 23, 2010
  15. Ferry HubertsNov 23, 2010
  16. Dun PealNov 23, 2010
  17. Andreas EricssonNov 24, 2010
  18. Dun PealNov 24, 2010
  19. Nguyen Thai Ngoc DuyNov 24, 2010
  20. Dun PealNov 24, 2010
  21. Robin RosenbergNov 28, 2010

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.