[SERVER-66765] Enable the SpiderMonkey JIT by default Created: 25/May/22 Updated: 06/Dec/22 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mohammad Dashti (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 150 | ||||||||||||||||
| Description |
|
Previously, we saw a lot of crashes when SpiderMonkey 60 JIT was enabled and we ended up turning it off in As part of this ticket, we want to investigate the possibility of turning JIT on by default. We have one proof point that SpiderMonkey Baseline JIT was unintentionally enabled on master between In addition, enabling Baseline JIT has shown a noticeable performance improvement for some performance tests (e.g., BF-25338), which justifies enabling it by default. There are several options for SpiderMonkey JIT (e.g., Baseline JIT, ION JIT, etc.) As part of this ticket, we want to enable the Baseline JIT by default. But, it makes sense to also evaluate the impact of more aggressive JIT engines in SpiderMonkey 91 and check whether they cause crashes or not. |