News for hackers. Stuff that matters.
Re:Introducing the WebKit FTL JIT by azakai on Tuesday May 13, 2014 @07:54PM (#7741343)
You can see some benchmarks comparing them here:

http://arewefastyet.com/#machine=12&view=breakdown&suite=asm...

http://arewefastyet.com/#machine=12&view=breakdown&suite=asm...

FTL beats v8 on almost all of those.

Re:Introducing the WebKit FTL JIT by yjbanov on Friday May 16, 2014 @12:14PM (#7756222)
All these benchmarks have "asmjs" in their names, which tells me they are not benchmarking idiomatic JavaScript, but JS generated by emscripten. If that's the case, they do not represent the performance of hand-written applications, which is the majority of all apps on the web.

It would be more interesting to see results for benchmarks such as DeltaBlue or Richards. These would correlate much better with gmail and hipmunk performance, as opposed to in-browser demos of Unreal Tournament.

Re:Introducing the WebKit FTL JIT by acqq on Wednesday May 14, 2014 @09:49AM (#7743671)
I wish I knew if lower is better or higher is better on the first page (y axis is not described on the graphs).
Re:Introducing the WebKit FTL JIT by azakai on Wednesday May 14, 2014 @11:25AM (#7744256)
Lower in the graphs is always better on awfy, which corresponds to lower numbers are better in all benchmarks, except for octane where higher numbers are better (the axis is reversed so still lower in the graph is better).