The AWFY "v8-turbofan <http://www.arewefastyet.com/#>" graphs don't show very useful data. They are generated from a testing-only configuration that was never indented to be used by embedders. TF is currently configured by default correctly on V8 tip of tree and since V8 4.1, so the plain "v8" graphs already include TurboFan's performance for the use cases where it is triggered.
I'd be amazed if you found TurboFan to be generally faster than "older V8" in any use cases other than asm.js code. TF doesn't yet implement many of the core optimizations that Crankshaft exploits to get "traditional" JavaScript code to run fast, e.g. anything that relies on deoptimization, like speculative type specialization. Danno On Thu Jan 15 2015 at 11:43:17 PM Flying Jester <[email protected]> wrote: > > I am wondering if they have been taking old svn as bleeding edge and > thus reporting wrong data, or the gap between turbofan and crankshaft is > really that much. Any comments? > > That would make sense to me. I have done a lot of work with TurboFan, and > I find it MUCH faster than older V8. > > -- > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > --- > You received this message because you are subscribed to the Google Groups > "v8-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
