Bug 931968 (Frame-Rate-Drop-DOM)

Frame Rate Drop Root Cause: DOM

RESOLVED WONTFIX

Status

DevTools
Performance Tools (Profiler/Timeline)
RESOLVED WONTFIX
5 years ago
10 days ago

People

(Reporter: Axel Kratel, Unassigned)

Tracking

Trunk
x86
Mac OS X
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [User Story], [mockup])

User Story

As a web app developer, I would like to be able to identify what DOM is associated with a drop in frame rates.

Acceptance Criteria:
* find in the recording places where frame rates drop
* Be able to see what type of graphical computing is going on: for example painting, rendering, reflows, etc...
* Bel able to see the DOM element associated with the graphical computing that takes a long time. 
* Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS).

Note: sister user story to 931959: Frame-Rate-Drop-JS. 

there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example:
* TIme spent in JS engine is short, but subsequent graphics consumption is high
* Time spent in JS engine is long, not necessarily associated with high graphics consumption.

Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
(Reporter)

Description

5 years ago
As a web app developer, I would like to be able to identify what DOM is associated with a drop in frame rates.

Acceptance Criteria:
* find in the recording places where frame rates drop
* Be able to see what type of graphical computing is going on: for example painting, rendering, reflows, etc...
* Bel able to see the DOM element associated with the graphical computing that takes a long time. 
* Be able to distinguish from external slow down causes versus problems my own app is causing. In other words the recording should be tab specific or app specific (FxOS).

Note: sister user story to 931959: Frame-Rate-Drop-JS. 

there are several scenarios that JS can cause slowdowns, we may want to break up this user story into the scenarios. For example:
* TIme spent in JS engine is short, but subsequent graphics consumption is high
* Time spent in JS engine is long, not necessarily associated with high graphics consumption.

Visualization could be done via time-based flame chart where every frame is broken down into where the browser spends time.
(Reporter)

Updated

5 years ago
Flags: pm-scrub?
(Reporter)

Updated

5 years ago
Component: Developer Tools → Developer Tools: User Stories
(Reporter)

Updated

5 years ago
User Story: (updated)
Component: Developer Tools: User Stories → Developer Tools: Performance Tools (Profiler/Timeline)
I believe these user stories are no longer relevant.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WONTFIX

Updated

10 days ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.