Profiler

From FirebugWiki

(Difference between revisions)
Jump to: navigation, search
m (Added __FORCETOC__ to always show the table of contents)
(Removed the description of the Memory Profiler because it was removed from FB 1.10)
 
Line 1: Line 1:
-
__FORCETOC__
+
The Profiler allows users to observe JavaScript activity and get statistics related to it.
-
The Profiler allows users to observe JavaScript activity and get statistics related to it. It's functionality is currently split into two parts - CPU profiling and memory profiling.
 
-
 
-
== CPU profiling ==
 
[[Image:Profiler.png|thumb|400px|CPU Profiler]]
[[Image:Profiler.png|thumb|400px|CPU Profiler]]
CPU profiling allows to get statistics about JavaScript function calls.
CPU profiling allows to get statistics about JavaScript function calls.
Line 30: Line 27:
| File || Name of the file plus line number, in which the function is located
| File || Name of the file plus line number, in which the function is located
|}
|}
-
 
-
== Memory profiling ==
 
-
[[Image:MemoryProfiler.png|thumb|400px|Memory Profiler]]
 
-
While CPU profiling concentrates on giving information about CPU activity, memory profiling returns data about RAM usage.
 
-
Memory profiling is currently disabled by default, because it is still in experimental state. It can be activated by setting <code>extensions.firebug.memoryProfilerEnable</code> to <code>true</code>.
 
-
You can [http://getfirebug.com/tests/issues/memory/test.html test] the different aspects of the Memory Profiler.
 
-
The information displayed after executing the Memory Profiler includes the following data:
 
-
{| class="wikitable" style="width:100%; vertical-align:top;"
 
-
|- bgcolor=lightgrey
 
-
! style="width:220px;" | Column || Description
 
-
|-
 
-
| Function || Name of the called function ("(?)" or "anonymous" for anonymous functions)
 
-
|-
 
-
| Calls || Number of calls to the function
 
-
|-
 
-
| explicit/js || Summarized amount of memory used for calls to the function
 
-
|-
 
-
| explicit/js/gc-heap || Summary of garbage-collected heap memory related to the function
 
-
|-
 
-
| explicit/js/tjit-data || Trace JIT memory used for calls to the function
 
-
|-
 
-
| explicit/js/mjit-code || Method JIT memory holding generated code used for calls to the function
 
-
|-
 
-
| explicit/images/content/used/raw || Memory used by in-use chrome images for calls to the function
 
-
|-
 
-
| File || Name of the file plus line number, in which the function is located
 
-
|}
 
-
 
-
Besides this information there is also a list shown containing all objects allocated while running the memory profiling session.
 
-
 
-
Note: Firefox has an integrated memory profiler. To access it type <code>about:config</code> into the address bar and hit <code class="key">Enter</code>.
 
== See also ==
== See also ==
-
[[Memorybug]] - Firebug extension for advanced memory profiling
+
[[Memorybug]] - Firebug extension for memory profiling

Latest revision as of 20:59, 22 April 2013

The Profiler allows users to observe JavaScript activity and get statistics related to it.

CPU Profiler

CPU profiling allows to get statistics about JavaScript function calls. This information includes the following data:

Column Description
Function Name of the called function ("(?)" or "anonymous" for anonymous functions)
Calls Number of calls to the function
Percent Percentage in time in comparison to all function calls within the profiling session
Own Time Time spent within the function (time spent within functions called by that function are not taken into account)
Time Summary of time spent within the function of all calls
Avg Average time for one call of the function
Min Minimal time spent within the function
Max Minimal time spent within the function
File Name of the file plus line number, in which the function is located

[edit] See also

Memorybug - Firebug extension for memory profiling

Personal tools