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/08/27 11:58:22 UTC

DO NOT REPLY [Bug 12073] New: - Regression: Extreme performance issue introduced with 2.3.0

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=12073>.
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=12073

Regression: Extreme performance issue introduced with 2.3.0

           Summary: Regression: Extreme performance issue introduced with
                    2.3.0
           Product: XalanJ2
           Version: 2.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: gs@qfs.de


My machine is an Intel P4, 800MHz, 512MB ram
Linux and Windows behaviour is similar

I'm transforming a relatively large source document (5MB)
xalan-J version 2.2 only takes a few seconds
xalan-J versions after 2.2, including 2.4-D1 take more than a minute

Profiling shows that almost all the time is spent before the actual
transformation takes place (I assume its spent building the DOM).

Behaviour is consistent from JDK 1.1 through JDK 1.3. I could not reproduce the
problem with JDK 1.4, even when trying to override bootclasspath to use the
newer xalan versions instead of the ones provided.

If anybody wants to look into this, please contact me and I'll provide the
relevant stylesheet and XML source.