Closed
Bug 1607930
Opened 6 years ago
Closed 6 years ago
Enable deferred allocation mode by default
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla74
Tracking | Status | |
---|---|---|
firefox74 | --- | fixed |
People
(Reporter: mgaudet, Assigned: mgaudet)
References
Details
Attachments
(1 file)
To allow simplifying future development on deferred allocation mode, we need to first enable it by default, then after it's been smoke tested for a while in nightly, we can get rid of the whole dual path system and simplify a bunch of things to make reasoning easier.
Updated•6 years ago
|
Priority: -- → P1
Assignee | ||
Comment 1•6 years ago
|
||
As a pre-flight check, this is a 10-repetition perfherder comparison between disabled-by-default and enabled-by-default
It appears there are no significant performance differences as hypothesized.
As well, this is a basic smoke test try run which shows things are doing well functionally.
Assignee | ||
Comment 2•6 years ago
|
||
Updated•6 years ago
|
Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
Pushed by mgaudet@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/24ac3bde10e0
Enable deferred allocation mode by default r=tcampbell
Comment 4•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox74:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
You need to log in
before you can comment on or make changes to this bug.
Description
•