Open Bug 1650056 Opened 4 years ago

Instrument bottlenecks in Console rendering with tracing markers

Categories

(DevTools :: Console, task, P3)

Product:
DevTools
Component:
Console
Type:
task

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

(In reply to :Harald Kirschner :digitarald from Bug 1634466 comment #0)

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.

In Bug 1634466, we landed an initial performance marker to track the ADD_MESSAGES action in profiles. This was done in the scope of performance investigations for MultiProcessBrowserToolbox slowness.

This follow up bug is here in case we want to add other markers.

You need to log in before you can comment on or make changes to this bug.