John Bandhauer wrote:
>
> Seth Spitzer wrote:
> >
> > As you know, a lot of the UI for Mozilla is written in JS.
> >
> > When using quantify, I frequently end up dead ending in js_Interpret and
> > and js_Invoke, which I assume means I'm back in my JS doing something.
> >
> > Is there a way to get the JS code to tell how many times I'm calling
> > each JS function, and even better, how long I spend in that function?
> >
> > To be clear, I don't think the performance problem is in the js engine,
> > I think it is in the mailnews JS.
> >
> > I could use that information to find performance problems in our JS.
> > I've found a few (by hand) but it would better to have numbers to know
> > where to look.
> >
> > -Seth
>
> See Syd's JS Profiler posting:
> news://news.mozilla.org/3978C430.6AA77AA5%40netscape.com
> It works on windows too, but you need to explicitly #define
> XPC_TOOLS_SUPPORT (uncomment the line in xpcprivate.h). I have
> not messed with this for a while, so there is potential for bit
> rot. Feel free to improve it!
>
> John.
Also, the bit about setting a pref is no longer accurate. The
prefs based config was removed to make the startup dependency
ordering happy. You have to set the output file using the
environment var. MOZILLA_JS_PROFILER_OUTPUT. See:
http://lxr.mozilla.org/seamonkey/search?string=MOZILLA_JS_PROFILER_OUTPUT
John.
