#33: Measure the impact of filling stack trace information when performing GO/RETURN/THROW ---------------------------+------------------------------------------------ Reporter: vvoutilainen | Owner: somebody Type: task | Status: closed Priority: minor | Milestone: unscheduled Component: component1 | Version: 1.0 Resolution: fixed | Keywords: exception ConditionThrowable go return throw performance ---------------------------+------------------------------------------------ Changes (by vvoutilainen):
* status: new => closed * resolution: => fixed
Comment:
Douglas R. Miles kindly did the measurement by using cl-bench, http://www.cliki.net/Performance%20Benchmarks. The benchmark CTAK showed a huge improvement, so the patch was decided to be good enough to commit. If some developer needs to have stack trace information in GO/RETURN/THROW, the fillInStackTrace override needs to be locally commented out in ConditionThrowable.java.
Committed in r11412.