Confirm
43
edits
Changes
Add notes to common causes of Base Content JS regressions
* An updated test focused on supporting fission. This measures the base overhead of an empty content process. It tracks resident unique, heap unclassified, JS, and explicit memory metrics as well as storing full memory reports as artifacts. The median value for each metric is used from across all content processes. It has much lower thresholds for alerting and is recorded in [https://wiki.mozilla.org/EngineeringProductivity/Projects/Perfherder Perfherder].
==== Possible regression causes ====
A change has caused more JavaScript to load at startup or into blank pages
* '''Common solution:''' lazily load any new modules you rely on
* '''Common solution:''' Split your code out to only load what is minimally needed initially
You modified the JS engine and it's using more memory
* '''Common solution:''' Attempt to reduce your object size for the common case, these tend to add up!
You implemented a new feature in JavaScript
* '''Common solution:''' Write the majority (or all of it) in compiled code (C++/Rust). This will reduce overhead and generally improve performance.
=== Explicit Memory summary ===
