Firefox/Projects/Startup Time Improvements/joelr notes: Difference between revisions

Line 6: Line 6:


=== September 16, 2009 ===  
=== September 16, 2009 ===  
==== I'm an idiot ====
I spent a month becoming an expert on DTrace, only to realize that it's not very useful to get a global picture of the bottlenecks because the overhead of tracing everything is so high!
Shark is a much better tool to get a global picture, specially using "Time profile all states" which allocates time spent blocking to the calling function. I overlooked this initially since I did not zero in on the right thread, the one that has ''start'' and ''XRE_main'' or ''exit''. Without this it looks like Firefox is spending most of its time waiting on threads and Mach messages.


==== Timing startup ====
==== Timing startup ====
109

edits