Record and display known performance hazards

NEW
Unassigned

Status

()

2 years ago
2 years ago

People

(Reporter: sfink, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
On https://developer.mozilla.org/en-US/docs/Mozilla/Benchmarking I am collecting a set of reasons why profiled builds may be substantially slower than release builds. It would be really nice if the gecko profiler could store enough information in the profiles to tell whether any of these things were in effect, and if so, prominently display that in the performance tab and in Cleopatra.
(Reporter)

Comment 1

2 years ago
For example, GC poisoning is a substantial slowdown. Some people claim async stacks are. Debug builds obviously are. I suspect a lot of profiling is done with inappropriate builds.
Depends on: 1326134
You need to log in before you can comment on or make changes to this bug.