Closed
Bug 931898
(record-frame-rate)
Opened 11 years ago
Closed 10 years ago
Recorded Frame rate visualization
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: akratel, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [User Story], [mockup] [c=devtools p= s= u=])
User Story
As a developer, I'd like to be able to have access to a visualization of the frame rate of my application in my instrumentation recording so that I can easily find the places where the application frame rate performs below par. Acceptance Criteria: * Browser instruments the frame rate * Instrumentation has minimal impact on performance * Tools provide a basic visualization of the frame rate that shows developers what is going on with the frame rate in their recording * Visualization UI should be extensible so that it's easy to add the right "click-throughs" to find root cause of frame rate slowdown. Notes: Related to 929114 where frame rate is visualized in real time, but this is different, the visualization should be a place where developers can now click through to actually map the slow down to a cause, see separate US for flame chart. See separate user stories for each type of root causes and different ways of visualization. Note that recorded frame rate visualization versus live frame rate visualization don't have to be the same UI, in fact, they should not be, because the two are very distinct usage contexts and will require different interaction modalities and different sizes. Related to 869245.
As a developer, I'd like to be able to have access to a visualization of the frame rate of my application in my instrumentation recording so that I can easily find the places where the application frame rate performs below par.
Acceptance Criteria:
* Browser instruments the frame rate
* Instrumentation has minimal impact on performance
* Tools provide a basic visualization of the frame rate that shows developers what is going on with the frame rate in their recording
* Visualization UI should be extensible so that it's easy to add the right "click-throughs" to find root cause of frame rate slowdown.
Notes:
Related to 929114 where frame rate is visualized in real time, but this is different, the visualization should be a place where developers can now click through to actually map the slow down to a cause, see separate US for flame chart. See separate user stories for each type of root causes and different ways of visualization.
Note that recorded frame rate visualization versus live frame rate visualization don't have to be the same UI, in fact, they should not be, because the two are very distinct usage contexts and will require different interaction modalities and different sizes.
Related to 869245.
Reporter | ||
Updated•11 years ago
|
Blocks: Frame-Rate-Drop-JS
Reporter | ||
Updated•11 years ago
|
Blocks: Frame-Rate-Drop-DOM
Reporter | ||
Updated•11 years ago
|
Flags: pm-scrub?
Comment 1•11 years ago
|
||
(In reply to Axel Kratel from comment #0)
> Related to 929114 where frame rate is visualized in real time, but this is
> different, the visualization should be a place where developers can now
> click through to actually map the slow down to a cause, see separate US for
> flame chart.
Is the idea that a fix for this bug would extend the fix for bug 929114 with additional UI to explain the cause? And that the bugs this one blocks describe specific UI additions that serve that purpose?
Reporter | ||
Updated•11 years ago
|
Component: Developer Tools → Developer Tools: User Stories
Reporter | ||
Updated•11 years ago
|
User Story: (updated)
Updated•11 years ago
|
Keywords: perf
Whiteboard: [User Story], [mockup] → [User Story], [mockup] [c=devtools p= s= u=]
Comment 2•10 years ago
|
||
I believe the new performance tool meets all this acceptance criteria -- closing
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: Developer Tools: User Stories → Developer Tools: Performance Tools (Profiler/Timeline)
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•