On Wed, Nov 24, 2010 at 11:34 AM, Andreas Ericsson <ae@xxxxxx> wrote: > How many refs (tags and branches) do you have? We have about 15 branches, but thousands of tags (we tag each release, and we make those often). However, I'm not sure how that could make `git status` slow, since it shouldn't care about tags at all? > Are the refs packed or loose? Packed. > If they are loose, does packing them resolve the issue? > Are you using network-mounted or local storage? Local storage on all workstations. One machine with those performance issues actually utilizes an incredibly fast, cutting edge SSD. It's twice as fast as the other slow machine, but 8s for `git status` is still slow. > What does the .git/config file look like for a user where git status > is excruciatingly slow? It's the normal .git/config you get by default on Git 1.7.x when cloning from a remote. I can paste it if you want, but doubt it will interest anyone: we didn't modify it. > Does copying the config file from a windows user to a linux user make > timings somewhat consistent between various systems? No. > Do older version of git perform as poorly? Yes. > How is the repository laid out (ie, are there any directories with > a ton of files in, or are they spread across multiple directories)? Generally spread across multiple directories. > How many .gitignore files are you using, and what do they look like? We're using 25 of those, >> However, after a reboot (of all things), `git status` latency >> skyrockets to 14-15s, making the repo unusable. > That's just plain weird, and is almost certainly a system issue. Yes, it's weird. I'm not sure it's a "system" issue since we're seeing it across a diverse set of Windows systems: Vista, Windows 7, pretty sure I saw XP as well, different hardware and software setups (different programs installed and running). .D -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html