I'm not sure what you were trying to test with the exception case -- exceptions only become a factor if they prevent some JIT optimization, and nothing there that would do that.
My experience is that exceptions kill performance from the point the first exception is raised, and it is really noticeable. In my language (ast interpreter, lisp-like), i've tried to add a debugger with stack traces/restarts based on exceptions. Things went like this: (server VM) (fib 30) naive, no exceptions: 0.484 msec exceptions catched, but none thrown: 0.515 msec after the first 3 or 4 exceptions: 0.720 msec (not kidding) After that point, the performance suffered consistently without mattering if exceptions were anymore thrown or not. -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=.
