Mozilla has reached an important Milestone as its new JavaScript engine “JaegerMonkey” is now faster than the current “TraceMonkey” in a key benchmark. Mozilla wants JaegerMonkey to be faster than the competition and launch on September 1, which means that JaegerMonkey will make it into Firefox 4.0.
does that mean the js engine isn’t part of the firefox 4 beta yet?
It feels pretty snappy already so if more improvements are on the way, it’s going to be great.
Yes, I think it’s not in the beta yet (atleast not when I tried last time, yesterday). And even if it was, it will probably not be enabled by default yet (needs some kind of about:config setting), like the old jit-options.
You can see if it’s been enabled if it has been compiled in, if you goto: about:buildconfig
If it includes the –enable-methodjit option ( https://wiki.mozilla.org/JaegerMonkey ) then it’s atleast available.
Edited 2010-07-16 00:34 UTC
AFAIK, Jaegermonkey is not in the Firefox 4 beta.
According to this page:
http://arewefastyet.com/
there are two parts to Jaegermonkey, those being the tracer JIT (orange) and method JIT (black), which have not yet been integrated into the one codebase. Moziila says these two parts are complementary, and that “once integrated, the merged branch will be faster than either branch individually”.
AFAIK, current builds of Mozilla do not have any form of JIT, and they are shown on the arewefastyet.com graphs as “moz w/o JIT (grey)”.
JaegerMonkey is just method JIT (black) and is indeed not in beta1. Tracing JIT (orange) is TraceMonkey, which is part of Firefox 3.6 already. Both engines excel at different things, that’s why combining them will be faster than each individually.
The target date for the integration of the new JavaScript engine is currently September the 1st.