Brendan Eich, Mozilla Chief Technology Officer, considers that the overall improvement score of 2x is an appropriate estimation for the current implementation, but he's certain this will further improve. "But this is only a start. With tracing, performance will keep going up. We have easy small linear speedup tasks remaining (better register allocation, spill reduction around built-in calls). We will trace string and regular expression code and break through the '2' barrier. We will even trace into DOM methods," he notes and Mike Shaver shares this opinion: "There are many wins left in each one of those benchmarks, and we'll be working on those through Firefox 3.1 and beyond: better code generation, more efficient guards, improvements to some data structures, parallel compilation, use of specific processor features, new optimization passes, tracing more code patterns, and many more".
Developers should note that TraceMonkey, while present in the latest nightly built of Firefox 3.1, is turned OFF by default. For testing purposes, an image manipulation demo page set up by Mike Schroepfer can be used; the corresponding screencast can be watched instead. More tech savvy users that are interested in the tracing technology can read the original Trace Trees paper or the the Hotpath paper.