On Tue, Nov 23, 2010 at 2:08 PM, Dun Peal <dunpealer@xxxxxxxxx> 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@xxxxxxxxx
martin@xxxxxxxxxx -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
--
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