[SERVER-30502] --disableJavaScriptJIT does not disable JIT Created: 03/Aug/17 Updated: 30/Oct/23 Resolved: 14/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | 3.4.10, 3.5.12 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mark Benvenuto | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | Platforms 2017-08-21 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
--disableJavaScriptJIT does not disable JIT because in MozJS 45+, the Ion JIT is on by default. In MozJS 38 and Mongo 3.2.x, the Ion JIT was not on by default. |
| Comments |
| Comment by Githook User [ 02/Oct/17 ] |
|
Author: {'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto', 'username': 'markbenvenuto'}Message: (cherry picked from commit b0338af0677ceb4a768033e179e278b4f3a280f2) |
| Comment by Githook User [ 14/Aug/17 ] |
|
Author: {'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}Message: |
| Comment by Kevin Pulo [ 04/Aug/17 ] |
|
Does this also affect the disableJavaScriptJIT server parameter? And would it be useful to have a --forceJavaScriptJIT flag (and/or server parameter), which sets the warmup trigger to 0? |