Mozilla is preparing to release a new JavaScript engine for Firefox
Today in the corporate blog Mozilla there was an entry by one of the key Firefox developers David Anderson (David Anderson) that the foundation is finishing the development of a new JavaScript engine codenamed IonMonkey. A wide range of users will be able to note an increase in browser speed on pages of complex web applications already with the release of Firefox 18, a beta version of which will be released on November 20.
IonMonkey's work will consist of three phases and look like this: first, translation into intermediate representation (intermediate representation (IR)) will be performed, various optimization algorithms will be applied to the result, and after that this IR will be translated directly into native code.
David honestly notes that he is not very pleased with the performance of such a solution, but this architectural approach makes it possible to conduct research on the effectiveness of the JavaScript compiler - it is much easier to take IR code, apply optimization algorithms to it and evaluate the result compared to its closest competitors.
To compare the performance of IonMonkey with other engines, David used Kraken and Google V8 benchmarks, running them on a MacBook Pro with Windows 7 Professional. In the first case, it turned out that the result of Firefox 17 has a result of 2602 ms, while Firefox 18 on IonMonkey - 1921 ms; in other words - 26% faster. Graphically, the result looks like this:
')
The benchmark of Mozilla's main rival, Google V8, was not forgotten either. Here, the test results are slightly smoother: Firefox 15 received 8474 points, Firefox 17 - 9511 and finally Firefox 18 - 10188 points (that is, 7% faster than Firefox 17). The graph in this case is as follows:
The remaining about two months before the launch of the beta version of Firefox 18 David intends to devote a number of optimization techniques to the introduction, which will be used for the IR-code.
[ Source ]
IonMonkey's work will consist of three phases and look like this: first, translation into intermediate representation (intermediate representation (IR)) will be performed, various optimization algorithms will be applied to the result, and after that this IR will be translated directly into native code.
David honestly notes that he is not very pleased with the performance of such a solution, but this architectural approach makes it possible to conduct research on the effectiveness of the JavaScript compiler - it is much easier to take IR code, apply optimization algorithms to it and evaluate the result compared to its closest competitors.
To compare the performance of IonMonkey with other engines, David used Kraken and Google V8 benchmarks, running them on a MacBook Pro with Windows 7 Professional. In the first case, it turned out that the result of Firefox 17 has a result of 2602 ms, while Firefox 18 on IonMonkey - 1921 ms; in other words - 26% faster. Graphically, the result looks like this:
')
The benchmark of Mozilla's main rival, Google V8, was not forgotten either. Here, the test results are slightly smoother: Firefox 15 received 8474 points, Firefox 17 - 9511 and finally Firefox 18 - 10188 points (that is, 7% faster than Firefox 17). The graph in this case is as follows:
The remaining about two months before the launch of the beta version of Firefox 18 David intends to devote a number of optimization techniques to the introduction, which will be used for the IR-code.
[ Source ]
Source: https://habr.com/ru/post/151374/
All Articles