DevTools/Features/JavaScriptProfiling: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=JavaScript Profiling
|Feature name=JavaScript Profiling
|Feature stage=Definition
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 20
|Feature health=OK
|Feature health=OK
|Feature status note=Demoed, but now the integration work begins.
}}
}}
{{FeatureTeam
{{FeatureTeam
|Feature product manager=Kevin Dangoor
|Feature product manager=Kevin Dangoor
|Feature feature manager=Kevin Dangoor
|Feature feature manager=Rob Campbell
|Feature lead engineer=Anton Kovalyov
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=A visualization of the run time of JavaScript code, to help developers identify bottlenecks and improve the responsiveness of their applications.
|Feature overview=A visualization of the run time of JavaScript code, to help developers identify bottlenecks and improve the responsiveness of their applications.
|Feature functional spec=This feature is based on the [https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler SPS profiler] that is now built-in and the Cleopatra frontend.
The initial implementation will be purposefully simple. Click to start profiling then click to stop. A visualization appears with a graph showing call stack depth over time. A table displays the various functions in which time was spent, allowing the user to drill into the stack.
|Feature implementation plan=See {{bug|795268}} for the details of the integration.
}}
}}
{{FeatureInfo
{{FeatureInfo
canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,093

edits

Navigation menu