Load JSONView converter-observer lazily via static component registration
Categories
(DevTools :: JSON Viewer, task)
Tracking
(firefox79 fixed)
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
(Keywords: perf-alert, Whiteboard: [overhead:19k])
Attachments
(1 file)
JSON View's content sniffing and converter components are currently registered in every process dynamically by a process script. This isn't ideal since it adds startup overhead and consumes somewhere over 10KB of memory in every content process, even when JSON View won't ever be used.
The easiest way to deal with this is to register both components statically, so that they're lazily loaded only when needed. For the content sniffer, this will unfortunately wind up causing it to load in every content process anyway, since we currently run content sniffers for every request in both the parent and content process. In the near(ish) future, though, we'll only run them in the parent, which means they'll never need to be loaded in the child.
| Assignee | ||
Comment 1•5 years ago
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Comment 4•5 years ago
|
||
== Change summary for alert #26253 (as of Wed, 17 Jun 2020 13:12:20 GMT) ==
Improvements:
1% Base Content JS windows10-64-shippable-qr opt 3,790,791.00 -> 3,771,757.33
0.49% Base Content JS macosx1014-64-shippable opt 3,734,215.50 -> 3,716,049.33
0.48% Base Content JS windows10-64-shippable opt 3,789,619.00 -> 3,771,424.67
0.31% Base Content JS linux1804-64-shippable-qr opt 3,713,216.00 -> 3,701,600.67
0.31% Base Content JS linux1804-64-shippable-qr opt 3,713,216.00 -> 3,701,753.67
0.29% Base Content JS linux1804-64-shippable opt 3,712,661.33 -> 3,701,724.33
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=26253
Updated•5 years ago
|
Updated•5 years ago
|
Description
•