Turn on --enable-perf by default for nightly builds
Categories
(Core :: JavaScript Engine, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox134 | --- | fixed |
People
(Reporter: denispal, Assigned: denispal)
References
(Blocks 1 open bug)
Details
Attachments
(5 external files)
Turning this feature on by default will be a big help when diagnosing problems in CI and Nightly. Currently we have to either push a separate build with --enable-perf so we get PGO training, or re-build this locally which may not always match the performance of a proper build.
There is some perf assessment that needs to be done to make sure enabling this doesn't regress anything.
Comment 1•2 years ago
|
||
Is there any privacy concerns that should be addressed with a data-review?
| Assignee | ||
Comment 2•2 years ago
|
||
(In reply to Nicolas B. Pierron [:nbp] from comment #1)
Is there any privacy concerns that should be addressed with a data-review?
Hmm, were you thinking of anything specific? I don't think there should be any privacy concerns. The intention is to build with --enable-perf by default on nightly so we can toggle jitdump output through an environment variable.
Comment 3•2 years ago
|
||
(In reply to Denis Palmeiro [:denispal] from comment #2)
(In reply to Nicolas B. Pierron [:nbp] from comment #1)
Is there any privacy concerns that should be addressed with a data-review?
Hmm, were you thinking of anything specific? I don't think there should be any privacy concerns. The intention is to build with
--enable-perfby default on nightly so we can toggle jitdump output through an environment variable.
I do not have anything specific in mind, just asking in case there is any probe which does any reporting without user interaction, such as adding information to the crash-dumps or telemetry.
| Assignee | ||
Comment 4•2 years ago
|
||
Ah, this is purely for local profiling so no client information will be collected by telemetry or crash dumps.
| Assignee | ||
Comment 5•2 years ago
|
||
| Assignee | ||
Comment 6•2 years ago
|
||
Depends on D226641
| Assignee | ||
Comment 7•2 years ago
|
||
We currently leak ExecutablePools if the perf spewer is enabled since perf maps cannot properly understand if an address region was reused.
Using jitdump, we now have load records so this should no longer be an issue.
Depends on D226642
| Assignee | ||
Comment 8•2 years ago
|
||
Depends on D226643
| Assignee | ||
Comment 9•2 years ago
|
||
The JitCodeAPI was initially planned to surface some PerfSpewer information to the Gecko Profiler, but it's currently unused and likely unneeded.
Depends on D226644
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 10•1 year ago
|
||
Comment 11•1 year ago
|
||
Backed out for causing build bustages @bug1875795.js.
Comment 12•1 year ago
|
||
Comment 13•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/014306ce6604
https://hg.mozilla.org/mozilla-central/rev/5e5d4534f1e0
https://hg.mozilla.org/mozilla-central/rev/82e8a7d7fce6
https://hg.mozilla.org/mozilla-central/rev/ff8540bd68df
https://hg.mozilla.org/mozilla-central/rev/e81aa9a01c77
| Assignee | ||
Updated•1 year ago
|
Description
•