Profiling can be a time intensive task, to optimizing your time using jsLex the following tips can be helpful.
- If profiling a large code base it is best to start with count metrics only. The additional burden of the profiling code will make your application perform poorly. Though the use of just counters is not a representative of where the overall time is being spent it is typically a good indication.
- Look to file to the code being profiled using jsLex. You can use the fileset tags inside the jsLex task to choose which files to profile.
- Added additional hand profiling code inside functions to see where the time being spent in native calls is occurring. You can either add jsLex.enterBlock(“”); or use the dojo.profile.start(“”);
- Customize the jsLex application parameters found documented here You will be running the application many time, this will save you some time.
- If you have any question just send an email to support [at] rockstarapps [dot] com.
