Closed
Bug 1541516
Opened 7 years ago
Closed 7 years ago
Allow instrumenting MozElement Custom Element performance using an environment variable
Categories
(Toolkit :: UI Widgets, task, P3)
Toolkit
UI Widgets
Tracking
()
RESOLVED
FIXED
mozilla68
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: bgrins, Assigned: bgrins)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
I believe it'd be useful in local development to track how long is spent inside of each Custom Element class, as a way to test if changes are helping or hurting performance.
Spinning this out of Bug 1515799 so it can be landed separately.
| Assignee | ||
Comment 1•7 years ago
|
||
If MOZ_INSTRUMENT_CUSTOM_ELEMENTS is set in the environment, then modify Custom Elements
to wrap each function and property lookup to keep a count and running time. Then print out
tables for each element at startup. Tables can be re-printed with MozElements.printInstrumentation().
| Assignee | ||
Updated•7 years ago
|
Type: defect → task
Updated•7 years ago
|
Priority: -- → P3
Pushed by bgrinstead@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a8c9a03ec27d
Instrument base custom element class and print call information in the console r=aswan
Comment 3•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•