FPS should be at '60' when not rendering

NEW
Unassigned

Status

()

4 years ago
4 years ago

People

(Reporter: BenWa, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Currently we can't aim to have the FPS counter at 60 because when we're idle we will stop counting. I suggested that devtools should do an empty refresh tick and count that in their measurement. We should do the same. It's a bit more complicated since we have 2 counters. If we continue to count during idle time than keeping the FPS at 60 means that we're idle which is a good thing.

Fixing this means that we could unconditionally ask people to keep the FPS counter at 60 which is good.
(Reporter)

Updated

4 years ago
Depends on: 1055050
(Reporter)

Updated

4 years ago
No longer depends on: 1055050
(Reporter)

Comment 1

4 years ago
If we fix this then there's two use case that the FPS counter will no longer solve:
- Knowing if we have needless recomposite. Currently the counter will stop/freeze and/or stay low. If we implement this then counter will not be useful to detect these problems.
- Knowing if we have an async animation/scrolling. Currently if the FPS counters are at 60 and 0-15 then you typically have async animation/scrolling.
You need to log in before you can comment on or make changes to this bug.