Profiling the Java Code

Mark Finkle mfinkle at
Tue Jan 21 07:29:37 PST 2014

Now that some improvements have been landing, I ran some newer profiles [1] for startup and pageload. Feel free to download them and load them into Montior/DDMS to look for new problem areas. I'll keep appending the date to the profile names so we can keep track over time. 


----- Original Message -----

> For many of the pageload performance bugs [1], we used profiles of the Java
> code to uncover the issues. This is just a quick post covering what you need
> to do in order to get profiles.

> 1. The Fennec build needs to be "debuggable" [2]. Nightlies are not, but
> local developer builds are.
> 2. For profiling pageload, you can generally use Monitor/DDMS [3]. Just press
> the "start method tracing" button, load a page, wait, press the "stop method
> tracing" button.
> 3. For profiling startup time, you really need to add
> Debug.startMethodTracing(...) and Debug.stopMethodTracing(). I added a
> simple patch [4] to show what I mean.

> I created some example profiles for startup and pageload. You can download
> them [5] and open them in Monitor/DDMS using the "File | Open File..." menu.

> [1]
> [2]
> [3]
> [4]
> [5]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the mobile-firefox-dev mailing list