Firefox OS/Performance/Profiling: Difference between revisions

Jump to navigation Jump to search
Line 1: Line 1:
= Profiling with the gecko profiler =
= Profiling with the gecko profiler =
Good at: Native stacks (with runtime options) + javascript profiling, low overhead sampling, familiar for gecko developers


See [https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Boot_to_Gecko_%28with_a_real_device%29 these instructions].  Patches are in-flight to get native stacks in profiles, but that's not in default configurations yet.
See [https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Boot_to_Gecko_%28with_a_real_device%29 these instructions].  Patches are in-flight to get native stacks in profiles, but that's not in default configurations yet.
= Profiling with systrace =
Good at: Shows process preemption, shows all calls to instrumented functions, Familiar for android developers
Bad at: Requires configure option, higher overhead
*Better instructions coming*.
Build with '--enable-systrace' and follow [http://developer.android.com/tools/help/systrace.html these instructions for systrace.py].
Confirmed users
336

edits

Navigation menu