search

mozilla-mobile / perf-frontend-issues

A repository to hold issues related to front-end mobile application performance.
4 stars 0 forks source link

Web extension doesn't meet RC on higher end devices - issue #12515 #135

Closed mcomella closed 3 years ago

mcomella commented 4 years ago

@MarcLeclair Please update with info for ecsmyth

sraturi commented 4 years ago

Here is some information I got for add-ons on MAIN from poking around add-ons channels

There is some extension work that happens immediately at startup, so you should see an effect even if you don't load any page some extensions like uBlock register listeners on every page load (to see if any given resource load should be blocked or not) so Gecko stalls network requests until the extension framework comes online to summarize: some work happens immediately, some at the first pageload. all depending on the add-ons

“The extension implementation is lazily loaded as much as possible, and some data is cached to reduce the cost of extension startup. For users, I suppose that blocking webRequest listeners (e.g. from uBlock Origin) are going to be a large contributor to perceived performance, because network requests are suspended until the extension has started + handled the request. Content scripts (especially with "run_at": "document_start") also have potential to affect performance of a web page.”

mcomella commented 3 years ago

Triage: we don't know which add-on to test with and haven't gotten an answer from the webExtensions team. Moving to main triage so we can review again next week.

mcomella commented 3 years ago

Triage: is this for pageload? Didn't meet page load RC? RC doesn't really matter right now. Most important thing for us is list of add-ons to test on start up. Only tested with ublock... should be no start up cost (besides ublock).

mcomella commented 3 years ago

Let's reopen when we deal with release criteria again – we're not quite sure what this is for.