WebKit + Squirrel Extreme + Acid3 + Vuela!

iBob · Mensaje por **iBob** » Dom Sep 28, 2008 2:40 am

La verdad que me dejó asombrado la velocidad de procesamiento del Squirrel Extreme (el motor javascript de safari/webkit) que acaban de integrar en el WebKit. No solo pasa 100% el Acid3 test, si no que ahora vuela impresionante. Capturé en video para que vieran...

http://nightly.webkit.org/

macpotok · Mensaje por **macpotok** » Mar Oct 21, 2008 11:58 pm

Al parecer el TraceMonkey de Firefox 3.1 vuela también:

http://www.genbeta.com/2008/09/11-activa-el-potente-tracemonkey-en-firefox-31-beta-minefield

Edit: Realmente vuela. Si se animan:

Bajen el beta de Firefox 3.1 acá: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-3.1b2pre.en-US.Mac.dmg
Luego de iniciado activen el TraceMonkey: http://www.genbeta.com/2008/09/11-activa-el-potente-tracemonkey-en-firefox-31-beta-minefield

Luego de reiniciar prueben lo liviano que es el nuevo Firefox y lo rápido que funcionan sitios con mucho JavaScript como GMail.

Respecto a WebKit estoy bajando también para comparar, gracias por el dato iBob.

iBob · Mensaje por **iBob** » Mié Oct 22, 2008 3:36 am

Probanding

macpotok · Mensaje por **macpotok** » Mié Oct 22, 2008 7:32 pm

Tracemonkey de Firefox 3.1 vs el motor Javascript de Firefox 3:

Imagen

Es muy interesante el concepto detrás de TraceMonkey, se podría ver una clara analogía con algunas predicciones que hacen los CPU.

John Resig escribió:How Tracing Works

In simple terms tracing works by watching for commonly-repeated actions (such as loops, function calls, or type checking) and tries to optimize their resulting native code into the lowest number of actions. The premise is rather simple - and it's an advance that we'll probably see proliferate to many interpreters and engines in the upcoming years.

Andreas Gal published a paper (PDF) on the subject and Brendan Eich has written up a TraceMonkey-specific explanation.

Some of the improvements made by tracing include:

* Function Inlining: Removing the overhead of function calls by simply replacing them with their resulting native code.
* Type Inference: Removing checks surrounding common operators (like "+") when the types contained within a variable are already known. This means that the engine will have already pre-determined, for example, that two strings need to be concated when it sees the "+" operator.
* Looping: The overhead of looping has been grossly diminished. It's one of the most common areas of overhead in JavaScript applications (common repetition of a task) and the constant determining of bounds and the resulting inner code is made negligible.

The code for this project has come from a number of places - one of which is coming from some code contributed to Mozilla, from Adobe: Tamarin Tracing, specifically the nanojit code that's able to work a lot of this just-in-time magic.

http://ejohn.org/blog/tracemonkey/