[armedbear-ticket] [armedbear] #33: Measure the impact of filling stack trace information when performing GO/RETURN/THROW

[armedbear]

#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:  0.22                                                    
 Component:  other         |     Version:  1.0                                                     
Resolution:  fixed         |    Keywords:  exception ConditionThrowable go return throw performance
---------------------------+------------------------------------------------
Changes (by ehuelsmann):

  * milestone:  unscheduled => 0.22


Old description:

> Douglas R. Miles reported recently that
> java.lang.Throwable.fillInStackTrace() can be a very time consuming
> operation when instantiating Throwables or objects the class of which
> extends Throwable.
>
> A patch for overriding the fillInStackTrace() function with an empty
> implementation was created, it seems to be a performance gain, but a
> benchmark is required. ANSI tests test so many other things that it's
> difficult to compare the impact of the patch without a test that tests
> only GO/RETURN/THROW.

New description:

 Douglas R. Miles reported recently that
 java.lang.Throwable.fillInStackTrace() can be a very time consuming
 operation when instantiating Throwables or objects the class of which
 extends Throwable.

 A patch for overriding the fillInStackTrace() function with an empty
 implementation was created, it seems to be a performance gain, but a
 benchmark is required. ANSI tests test so many other things that it's
 difficult to compare the impact of the patch without a test that tests
 only GO/RETURN/THROW.

--

Comment:

 closed is not 'unscheduled'; moving to the most recently closed milestone.

-- 
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/33#comment:2>
armedbear <http://common-lisp.net/project/armedbear>
armedbear