Profile startup time and investigate optimizations

NEW
Unassigned

Status

3 years ago
2 months ago

People

(Reporter: jlong, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
After bug 1132501, we took a hit on startup and closing time. Here's a list of regressions: http://alertmanager.allizom.org:8080/alerts.html?rev=256e3e81fed77b17ea9158786a349698bb59a6ab&showAll=1&testIndex=0&platIndex=0

In the DAMP tests we did on the try run, it looks like `close` tests took the hardest hit, so I'm not sure if this is as big of a deal as it looks. I'm trying to figure out where to look at the subtests on mozilla-central. It could be that detaching the thread is slow, so closing the devtools took a hard hit, but opening isn't as bad.

Either way, we should probably look at everything that is happening on startup and see if there's anything we can optimize.
(Reporter)

Comment 1

3 years ago
I'm not going to have much time on this for the next couple weeks, but I'll keep it in mind.
Not sure why this is in "Developer Tools: Framework". Moving to the debugger component for triage. Although I'm not sure how we can prioritize that now.
Component: Developer Tools: Framework → Developer Tools: Debugger

Updated

2 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.