Closed
Bug 1634466
Opened 5 years ago
Closed 4 years ago
Instrument bottlenecks in Console rendering with tracing markers
Categories
(DevTools :: Console, task, P3)
DevTools
Console
Tracking
(firefox80 fixed)
RESOLVED
FIXED
Firefox 80
| Tracking | Status | |
|---|---|---|
| firefox80 | --- | fixed |
People
(Reporter: Harald, Assigned: jdescottes)
References
(Blocks 3 open bugs)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Profiles shared in reports for slow console and browser console point to slow code without the context on what was being processed and what the state of the console was.
Questions that came up: When was the first UI displayed? How many messages were displayed initially? How were messages chunked? How many messages were added?
The new tracing markers can help here to provide near-zero-overhead instrumentation to improve profiles.
|
Reporter | |
Updated•5 years ago
|
Summary: Instrument bottlenecks in Console rendering with markers → Instrument bottlenecks in Console rendering with tracing markers
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Pushed by jdescottes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d862bc72d977
Add a simple performance marker to capture the number of messages added r=nchevobbe
|
|
Assignee | |
Comment 3•4 years ago
|
||
I probably should have filed a dedicated bug for this. Will open a follow-up in order to tackle additional markers
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 80
You need to log in
before you can comment on or make changes to this bug.
Description
•