Slashdot Mirror

I don't think it's all that useful to compare the JavaScript engine in Firefox's beta releases to other engines at this stage. JaegerMonkey, Mozilla's new method JIT compiler, is not yet integrated into the beta releases. JaegerMonkey is making steady progress in improving performance and in a couple of months or so will likely be on par with Nitro and V8. See http://arewefastyet.com/ for charts of JaegerMonkey's progress and for a breakdown of each of the individual tests see http://arewefastyet.com/individual.php. The regress chart is interesting to see the performance gains to be had when TraceMonkey and JaegerMonkey are used in combination.

I don't think it's all that useful to compare the JavaScript engine in Firefox's beta releases to other engines at this stage. JaegerMonkey, Mozilla's new method JIT compiler, is not yet integrated into the beta releases. JaegerMonkey is making steady progress in improving performance and in a couple of months or so will likely be on par with Nitro and V8. See http://arewefastyet.com/ for charts of JaegerMonkey's progress and for a breakdown of each of the individual tests see http://arewefastyet.com/individual.php. The regress chart is interesting to see the performance gains to be had when TraceMonkey and JaegerMonkey are used in combination.

I don't think it's all that useful to compare the JavaScript engine in Firefox's beta releases to other engines at this stage. JaegerMonkey, Mozilla's new method JIT compiler, is not yet integrated into the beta releases. JaegerMonkey is making steady progress in improving performance and in a couple of months or so will likely be on par with Nitro and V8. See http://arewefastyet.com/ for charts of JaegerMonkey's progress and for a breakdown of each of the individual tests see http://arewefastyet.com/individual.php. The regress chart is interesting to see the performance gains to be had when TraceMonkey and JaegerMonkey are used in combination.

Seeing as how it's not listed on the benchmark page, I doubt it.
And Apple Nitro without JIT is almost as good as Tracemonkey with JIT.

http://arewefastyet.com/

NO.

(But it's getting good! - that Firefox javascript engine performance day-to-day or almost performance improvement graph)

The tracer JIT is able to compile most methods into very tight assembly code because it is able to determine the types of each variable at compile time. For the methods that can't be compiled with the tracer JIT, they have been run by the interpreter, which is very slow compared to JIT compilers. With the new method JIT, methods that can't be compiled with the tracer JIT will be run by the method JIT instead of the interpreter. This is the meaning of the statement the tracer JIT (orange) and method JIT (black) are not yet integrated. once integrated, the merged branch will be faster than either branch individually. they are complementary.

I think you're missing the point of what is being benchmarked. Mozilla hasn't released benchmarks of their new JS engine with both "method" and "tracer" JIT combined. They are being evolved separately, but are (according to Moz) complementary. Thus, we don't know how far they actually are from their goal yet.

Check out http://www.arewefastyet.com/ for benchmarks and description.

From what I can gather from the associated bug report, the "fatval" optimizations are also not applied to the portions of JS code that is traced... which would imply that the better job the tracer engine does, the less the "fatval" optimizations are applied.

The result is that an unknown "free" speed increase is waiting in the wings. What the magnitude of this increase is... well, that's the question, isn't it?

Does 1 September seem like a really tight deadline? Yes, sure does, but more in terms of stability and robustness than actually getting to a specific speed milestone.

Actually Mozilla uses the same terminology. See any of the data points on the graphs located at the Mozilla run: http://www.arewefastyet.com/

For those of you who want to track the progress of Mozilla's JS efforts, visit the self-descriptive ARE WE FAST YET?