Javascript Performance Thread

[WonderCsabo]

We wont see a performance boost, because the AWFY page uses Firefox builds witch already contain TI.

[dao-g]

We wont see a performance boost, because the AWFY page uses Firefox builds witch already contain TI.

http://arewefastyet.com/?a=b&view=regress does, http://arewefastyet.com/ doesn't.

[greg86]

where did u see a boost on http://www.arewefastyet.com/?a=b&view=regress&runs=300 ???
i only see regressions since middle of august

[dbcooper.dk]

Great, next would be to further optimize for V8 benchmarks to wipe the smug face off Chrome.

That will come with the implementation of incremental and generational GC.

[Ver Greeneyes]

The main page will display the TI-enabled results once bug 683410 lands.

[Blechnum]

Finally something happening!
Here is what I'm seeing (compared to two days ago): V8 improved from 4109 to 4607, Kraken improved from 5351.2 ms to 4573.1 ms and Sunspider also went down from 258 ms to 246.3 ms. Nice. But Peacekeaper took a turn for the worse I'm afraid: the score went down from 5241 to 4671.
There are also regressions in some of the subtests in Kraken and V8 but I don't got the numbers.
Oh well, at least things are moving again.

[WonderCsabo]

I think the about:config pref for TI should contain the word "jit". In that case, you can search for "jit", and all JS engine prefs come up.
I remember some dev suggested the same for profiling. Guys, do you think it worths opening a bug?

[Mark342]

Make sure you guys are testing the latest version of V8 (version 6) when comparing inference on/off
javascript.options.typeinference set to true:
V8: 5472
Highest scores:
Crypto: 13707
DeltaBlue: 10546

other scores:
Richards: 7692

Sunspider: 232.4ms +/- 0.9%

Kraken: 3961.6ms +/- 0.6%

---------------------------------------------------
javscript.options.typeinference set to false:
V8: 4193
Highest scores:
Richards: 6563
Crypto: 5816

Other scores:
DeltaBlue: 4708

Sunspider:
260.1ms +/- 2.0%

Kraken:
5322.7ms +/- 0.4%
--------------------------------------------

Note: the browser must be restarted for javascript.options.typeinference to take affect

[UrbenLegend]

Seems like there's a performance regression for http://bellard.org/jslinux/

It used to boot up in 6 seconds. Now with TI it boots up in 13 seconds.

EDIT: Found bug https://bugzilla.mozilla.org/show_bug.cgi?id=670885

[nadark]

Make sure you guys are testing the latest version of V8 (version 6) when comparing inference on/off
javascript.options.typeinference set to true:
V8: 5472
Highest scores:
Crypto: 13707
DeltaBlue: 10546

other scores:
Richards: 7692

Sunspider: 232.4ms +/- 0.9%

Kraken: 3961.6ms +/- 0.6%

---------------------------------------------------
javscript.options.typeinference set to false:
V8: 4193
Highest scores:
Richards: 6563
Crypto: 5816

Other scores:
DeltaBlue: 4708

Sunspider:
260.1ms +/- 2.0%

Kraken:
5322.7ms +/- 0.4%
--------------------------------------------

Note: the browser must be restarted for javascript.options.typeinference to take affect

I think I read somewhere that there's some overhead for including TI in the browser and turning off the pref only doesn't get rid of it due to the complexity of the code needing a lot of changes in the javascript engine to work , since most people don't run with TI disabled. If you could, could you test with the build just before TI landed on the trunk.

[dutchguy]

They removed the 'old' engines from the regression page

[Zlip792]

Is TI graph is in actual (JM+TI) graph? or JM+TI will be added later?

[iwod]

Anyone know when is Incremental GC landing? It seems to be read and finished

https://bugzilla.mozilla.org/show_bug.cgi?id=641027

But dont know what is stopping it to land.

[Astrophizz]

They also removed the 'old' engines from the regular page and didn't replace it with TI...

[phuzi0n]

Is Firebug killing javascript performance after TI landed for anyone else? I tried updating to the latest stable Firebug 1.8.2 and then to 1.9.0a1 but it still slows down v8 benchmark by ~4x and sunspider by ~2x. I made sure that Firebug's javascript profiling is disabled (with Firebug profiling enabled v8 is ~10x slower).