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

Re: git status takes 30 seconds on Windows 7. Why?

From
Jeff King <peff@peff.net>
Date
Mar 27, 2013, 19:04 UTC
Message-ID
<20130327190425.GA26380@sigill.intra.peff.net>
In-Reply-To
<20130327184657.GP2286@serenity.lan>
On Wed, Mar 27, 2013 at 06:46:57PM +0000, John Keeping wrote:
> I think the simple reality is that Git was written with the assumption
> that stat is cheap and that isn't really the case on Windows, where the
> filesystem cache doesn't seem to do that well with this.

Yes, I think that's pretty much the case (though most of my Git-on-Windows experience is from cygwin long ago, where the stat performance was truly horrendous). Have you tried setting core.preloadindex, which should run the stats in parallel?

-Peff
Previous: John KeepingNext: Linus Torvalds
Message 7 of 12 in “git status takes 30 seconds on Windows 7. Why?”
  1. Jim KinsmanMar 27, 2013
  2. Andreas EricssonMar 27, 2013
  3. Konstantin KhomoutovMar 27, 2013
  4. Matthieu MoyMar 27, 2013
  5. Jim KinsmanMar 27, 2013
  6. John KeepingMar 27, 2013
  7. Jeff KingMar 27, 2013
  8. Linus TorvaldsMar 27, 2013
  9. Junio C HamanoMar 27, 2013
  10. Linus TorvaldsMar 27, 2013
  11. John KeepingMar 27, 2013
  12. Duy NguyenMar 28, 2013

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.