You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/12/11 15:26:52 UTC
DO NOT REPLY [Bug 14522] -
Performance problem due to unnecessary ArrayIndexOutOfBoundsException
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14522>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14522
Performance problem due to unnecessary ArrayIndexOutOfBoundsException
------- Additional Comments From dminard@objectiveEdge.com 2002-12-11 14:26 -------
I agree that the null handle case *should* be uncommon and that the higher
level code should be considered to see why some cases lead to the performance
degradation that I've experienced.
I find it difficult to believe that a profiling tool would show the cost of a
null test to be significant. I've never seen such an indication from any
profiling tool. Perhaps I would observe a net performance loss (as you
remembered observing) if I were to consider all the numerous modes that JVMs
can be run in...interpreted mode maybe?
Regardless, I will endeavour to produce a full test case for this bug so
someone with more comprehensive xalan development experience might attempt to
address this issue at the higher level.