Version 9, changed by carlavmott 02/02/2007. Show version history
Profiling is the term for looking at where time is spent by any Javascript code. If you have a problem with code taking too long, then it helps to use a profiling tool to diagnose exactly where all the time is being used.
When using some profiling tools you may need to use debugAtAllCosts and not a packaged version of dojo (see DebuggingJavascript). Using debugAtAllCosts will enable the profiling tool to allocate time spent per function to the correct source file -- otherwise you will end up with the elapsed times being allocated to anonymous functions which will make it difficult for you to understand!
Also make sure you have used any relevant PerformanceTuning techniques before you start profiling.
Free but a bit buggy to use. I have found it easiest to get into debugging mode with Venkman by using a debugger keyword in your sourcecode. Run the Venkman debugger, then run your code and it will stop at the breakpoint.
Venkman contains a profiling tool, although the reports are a bit difficult to use. It does work.