On Wed, Jun 01, 2011 at 07:31:57PM -0400, Joey Hess wrote: > Cold cache: > [...] > 28.846625099 seconds time elapsed > > Warm cache is 0.88 seconds, but cold cache is typical; I use a cheap netbook > for a lot of different stuff. Yeah, it is going to be painful on a cold cache. But I wonder whether your workflow would really permit the "reset" thing to make a difference. That is, are you doing "git reset -- file" from a cold cache, and then doing _nothing_ else with git? Because while yes, it may be annoying for the "reset" to take 30 seconds, it's warming the cache so that the subsequent "diff" or "status" will take 29.1 seconds less. Which isn't to say I'm not sympathetic to the performance problems of large repos on a cold cache. But I'm not sure there's really a way around that. You're going to want to see the stat information eventually if you are doing anything meaningful with git, and once it's loaded, the warm cache delay isn't too bad. Trying to avoid it seems like a losing battle. -Peff -- 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