On Tue, Mar 27, 2012 at 1:54 AM, Tim Oxley <[email protected]> wrote: > I recall seeing a v8 dev talking about how try-catch prevents certain types > of optimisations on the code it contains, and I notice that for many sites > (coming from nodejs perspective) V8 can spend a lot of time in JSON.parse… > and because it throws if it comes across some malformed JSON, you always > have to have the thing inside a try/catch… therefore always suffering from > not being able to optimise due to try catch. > > Is that a valid concern?
This should not affect JSON.parse, only the function that calls it. You can keep an eye on this with --trace-opt --trace-bailout > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- Erik Corry, Software Engineer Google Denmark ApS - Frederiksborggade 20B, 1 sal, 1360 København K - Denmark - CVR nr. 28 86 69 84 -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
