Migrate finding in scope locations from Babel to lezer
Categories
(DevTools :: Debugger, task)
Tracking
(firefox137 fixed)
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | fixed |
People
(Reporter: ochameau, Assigned: bomsy)
References
(Depends on 1 open bug, Blocks 2 open bugs)
Details
(Keywords: perf-alert)
Attachments
(1 file)
Babel parser (parser-worker.js) is by far the main performance culprit of the Debugger.
We do use the parser for various debugger frontend features, highlighted in the following document:
https://docs.google.com/document/d/12xq6Q5qDEuNDtKwSm9LwKSUA4k_zT-r96-3TWIimoqA/edit#heading=h.ldmzcj1wna5e
Thanks to the migration to CodeMirror 6 (bug 1773246), we will be able to use its new parser lezer.
This parser supports parsing only chunks of code and will allow us to only parse the current viewport.
Babel only supports parsing the whole file, which is the main reason why this particular part of the debugger is slow.
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Backed out for causing multiple dt failures
There are also failures with log parsing skipped like this one
Backed out for causing multiple dt failures
| Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
(In reply to Norisz Fay [:noriszfay] from comment #3)
Backed out for causing multiple dt failures
There are also failures with log parsing skipped like this one
Perfherder has detected a devtools performance change from push a9fff10eecc6201bd71902ca278a3da19765c942.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 11% | damp custom.jsdebugger.open-large-minified-file.DAMP | linux1804-64-shippable-qr | e10s fission stylo webrender | 63.40 -> 56.55 |
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 43886
For more information on performance sheriffing please see our FAQ.
Updated•1 year ago
|
Description
•