Defer allocation of JSFunctions until after Parsing is done.
Categories
(Core :: JavaScript Engine, enhancement, P1)
Tracking
()
People
(Reporter: mgaudet, Assigned: mgaudet)
References
Details
Attachments
(10 files, 5 obsolete files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
To further our goal of decoupling the parser for the GC, we'd like to be able to avoid creating JSFunctions until after the parser is done its business.
Assignee | ||
Comment 1•6 years ago
|
||
Depends on D38699
Assignee | ||
Comment 2•6 years ago
|
||
Depends on D39769
Assignee | ||
Comment 3•6 years ago
|
||
Depends on D39770
Assignee | ||
Comment 4•6 years ago
|
||
Depends on D39771
Assignee | ||
Comment 5•6 years ago
|
||
Depends on D39772
Assignee | ||
Comment 6•6 years ago
|
||
Depends on D39773
Assignee | ||
Comment 7•6 years ago
|
||
Depends on D39774
Assignee | ||
Comment 8•6 years ago
|
||
Remaining are the stand-alone parses, and a dummy function allocation
for Asm.JS I think
Depends on D39775
Assignee | ||
Comment 9•6 years ago
|
||
Kicked off some Performance test results (--rebuild=10
)
-
AWSY Results: No major memory impacts
-
Raptor Results: almost all results are low confidence with the exception of two webaudio tests which see 2% degradations. It does seem like there's something real here, as there's some high confidence degradations reported in the subtests. I do think that the extreme quantization of the scores suggests the effect may be magnified by quantization though.
Assignee | ||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
Assignee | ||
Comment 11•6 years ago
|
||
Depends on D39776
Assignee | ||
Comment 12•6 years ago
|
||
Updated•6 years ago
|
Comment 13•6 years ago
|
||
bugherder |
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
Comment 16•6 years ago
|
||
Backed out on request
Push with build bustages: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception&revision=eb0b2f561461461e5dde736180a463ee297e13be&selectedJob=259460806
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=259460806&repo=autoland&lineNumber=7406
Backout: https://hg.mozilla.org/integration/autoland/rev/be22f622aeead6c162ab348c1daec5d2401bd7d8
Comment 17•6 years ago
|
||
There are also all types of test failures on this push and the next one:
and
Comment 18•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 19•6 years ago
|
||
This makes eager processing the default as well, which makes the code
effectively work how it does before the FunctionTree patches.
Depends on D39774
Assignee | ||
Comment 20•6 years ago
|
||
Assignee | ||
Comment 21•6 years ago
|
||
Comment 22•6 years ago
|
||
bugherder |
Comment 23•6 years ago
|
||
Comment 24•6 years ago
|
||
bugherder |
Comment 25•6 years ago
|
||
Comment 26•6 years ago
|
||
Depends on D41060
Comment 27•6 years ago
|
||
I'm doing some follow-up tweaking that we didn't get finished before Matt went on leave. One important detail is that the current code in mozilla-central always runs in 'eager' mode which matches the existing parser behaviour. There is no immediate win with just the parser decoupled, so we will take a little more time to iterate on it.
Comment 28•6 years ago
|
||
Comment 29•6 years ago
|
||
bugherder |
Assignee | ||
Updated•6 years ago
|
Description
•