I usually use Process Explorer, but honestly for these noticable dealys I can use an old fashioned stopwatch. I'm just not the kind of person who's going to get excited about the difference between 2.000 and 2.005 seconds No, really, I'm not making fun of the Git people. :) I realize there is sometimes interesting information in the decimal places, but my perspective is entirely pragmatic. As Eli says, VMMap is also very helpful on Windows: <a href="http://technet.microsoft.com/en-us/sysinternals/dd535533">http://technet.microsoft.com/en-us/sysinternals/dd535533</a> ~M <div class="gmail_quote">On Wed, May 11, 2011 at 12:44 AM, Alexander Belchenko <<a href="mailto:bialix@ukr.net">bialix@ukr.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Martitza Mendez пишет:<div><div></div><div class="h5"> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On Mon, May 9, 2011 at 10:20 PM, John Arbash Meinel <<a href="mailto:john@arbash-meinel.com" target="_blank">john@arbash-meinel.com</a> <mailto:<a href="mailto:john@arbash-meinel.com" target="_blank">john@arbash-meinel.com</a>>> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... >> Maximum memory consumption during commit was 315MB. Total page faults >> about 800,000 (on a machine with 2GB RAM). > > What is "Total page faults"? A page fault is when a program wants to access a bit of virtual memory but it isn't actually present in memory. <a href="http://en.wikipedia.org/wiki/Page_fault" target="_blank">http://en.wikipedia.org/wiki/Page_fault</a> This happens in a variety of contexts. One is during "swapping", when the OS runs out of memory and writes the virtual pages to disk. Then when the program accesses them again, it has to read back from disk. I *think* it might also happen based on how you allocate. I know in Linux you can do tons of mallocs(), but until you touch the memory it doesn't actually assign real memory to your process. I believe you don't hit a page fault during malloc() just during the later access. This set of observations was on WinXP (I should have mentioned that). And I'm actually not sure whether or how 'lazy' memory allocation is on WIn32. Good question. I suppose I should know. I'll have to test that when I get a few minutes. </blockquote> </div></div> Which tools are you using to get such statistics? Process Explorer? -- All the dude wanted was his rug back </blockquote></div>