Comment #2 on issue 1065 by [email protected]: try catch incurs an
unexpected performance penalty
http://code.google.com/p/v8/issues/detail?id=1065
I've been reading about this, and a lot of sources mention that variables
are allocated on the heap rather than the stack, which is the source of the
performance problem. My question is: *why* is this done? Why not unwind the
stack like other langauges do?
It looks like even simply wrapping the try block's code in a function call
removes almost all the performance hit. Why can't the principles at play
there be exploited to speed this stuff up?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
