Who's optimizing for a specific version of V8? Avoiding inherently slow things (such as for-in loops over slow objects, or needless polymorphism, etc) in your JS code makes a lot of sense regardless of the VM you're running on. Sure, some deopts may no longer happen in an upcoming version, but then again maybe they still will, and maybe you want better performance *now* rather than possibly at some unspecified date in the future.
On Thu, Oct 11, 2012 at 5:46 PM, Michael Schwartz <[email protected]> wrote: > Is it really a good idea to optimize for a specific version of v8? I > mean, something you spend a bit of time hand optimizing could be a > completely irrelevant optimization in some upcoming v8 release. It could > even be slower. > > Or am I wrong? :) > > On Oct 11, 2012, at 2:48 AM, Christoph Sturm <[email protected]> > wrote: > > I'm trying to optimize my node app with --trace-deopt > > how do i see why the method is deopted? for example here: > > **** DEOPT: Wlbl.Checker.checkUrl at bailout #24, address 0x0, frame size > 88 > [deoptimizing: begin 0x25d8e5e85e71 Wlbl.Checker.checkUrl @24] > translating Wlbl.Checker.checkUrl => node=260, height=40 > > also when i log optimizer bailouts, i see this: > Bailout in HGraphBuilder: @"exports.paramsToString": ForInStatement is not > fast case > > does that mean i should replace the for in with a for loop that iterates > over Object.keys? > > thanks > chris > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
