Open
Bug 1055046
Opened 11 years ago
Updated 3 years ago
FPS should be at '60' when not rendering
Categories
(Core :: Graphics, defect)
Tracking
()
NEW
People
(Reporter: BenWa, Unassigned)
References
(Blocks 1 open bug)
Details
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 | ||
Comment 1•11 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.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•