Open
Bug 1298117
Opened 8 years ago
Updated 2 years ago
Record and display known performance hazards
Categories
(Core :: Gecko Profiler, enhancement, P3)
Core
Gecko Profiler
Tracking
()
NEW
People
(Reporter: sfink, Unassigned)
References
Details
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•8 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.
We now display a warning for debug builds, but there could be more.
Severity: normal → N/A
Type: defect → enhancement
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•