Closed Bug 1929003 Opened 1 year ago Closed 11 months ago

Make the DevTools tracer button use the native profiler pipeline

Categories

(DevTools :: Debugger, enhancement)

enhancement

Tracking

(firefox134 fixed)

RESOLVED FIXED
134 Branch
Tracking Status
firefox134 --- fixed

People

(Reporter: ochameau, Assigned: ochameau)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Bug 1911021 reverted back the tracer controlled from DevTools to manually generate the profile via Spidermonkey hooks.

We should make the DevTools tracer icon use the new native profiler pipeline to gather tracing profiles.

Blocks: 1929004

Stop manually crafting the profiler data by using SpiderMonkey hooks.
Instead, use the profiler native pipeline to do the collection.

This still relies on JSTracer class in order to trigger the record on next interaction or page load.
One caveat is that it starts the profiler from the content process, which prevents recording screenshots correctly.

Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED
Pushed by apoirot@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cd1c6516429a [devtools] Use native profiler to collect JS Traces from DevTools. r=dthayer
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch

Perfherder has detected a devtools performance change from push 1bb3c36a15c39849a61394f997225808d6c215b5.

Improvements:

Ratio Test Platform Options Absolute values (old vs new)
45% damp jstracer.profiler-recording-performance.DAMP macosx1015-64-shippable-qr e10s fission stylo webrender 519.44 -> 286.36
37% damp jstracer.profiler-recording-performance.DAMP windows11-64-shippable-qr e10s fission stylo webrender 250.19 -> 156.97
29% damp jstracer.profiler-recording-performance.DAMP linux1804-64-shippable-qr e10s fission stylo webrender 710.70 -> 506.90

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run these tests on try with ./mach try perf --alert 42500

For more information on performance sheriffing please see our FAQ.

Blocks: 1931364
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: