1482392 - Track webextension Javascript activity

Status: RESOLVED WONTFIX

(Toolkit :: Performance Monitoring, enhancement, P2)

Description

[Tarek Ziadé (:tarek)]

Let's add a counter that will receive duration values and event loop iterations (==dispatches), 
so we know how long a webext spends in the JS runtime.

current implementation plan:

- add a global hashtable [WebExtensionId / duration+dispatch] 
- add in the runtime performanceMonitoring a set of functions so we can label it with the WebExtensionId
- in XPCJSRuntime::Initialize, if the principal has an addonId, create an entry in the table and flag the context runtime with it
- in AutoStopwatch, if the cx is flagged, we can measure the time spent via enter/leave (and iterations)

For the consumers, create a promise that asks all processes their global hashtable, and returns a merged, JS-friendly array, exposed via the extension framework.

Comment 1

[Tarek Ziadé (:tarek)]

related : bug 1309946 - which was the previous implementation of the "This addon might slow down etc..."

Comment 2

[Tarek Ziadé (:tarek)]

related : bug 1406872 -- it can probably be done in the same patch

Comment 3

[Tarek Ziadé (:tarek)]

Attachment: Bug 1482392 - Track Web Extensions Javascript activity - r?jandem,baku,florian

This is a first draft for the patch that tracks WebExtension JS
activity, for early feedback.

Comment 4

[Tarek Ziadé (:tarek)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=bd55aed4f46e460bbb02013966e8b7f849992010

Comment 5

[Tarek Ziadé (:tarek)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=cb735d195d6f6a432870bc5ca7a5806d61d84b39

Comment 6

[Tarek Ziadé (:tarek)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=fc650844dd5e6aee27367018476251ee8f290f63

Comment 7

[Tarek Ziadé (:tarek)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=c54ce0adc56b2660d94416ff8a386df992646754

Comment 8

[Tarek Ziadé (:tarek)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=916a4ce35de014dc96c8468938ae439b62717601