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=6463>. 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=6463 Severe Performance problems (Memory + Time taken) compared to SAXON ------- Additional Comments From [EMAIL PROTECTED] 2002-02-15 16:52 ------- Well... I've confirmed the fact that we're nesting open RTFs _very_ deeply... which explains the storage costs; essentially, you're building up a gawdawful stack of pending DTMs, since the shared DTM code insists that one document be closed before starting another in the same DTM. We could try to make SAX2RTFDTM's construction process interruptable, to avoid that context switch... This looks likely to be ugly, but doable. Of course this is a particularly ugly stylesheet. I'm tempted to spend some time looking for a more XSLT-like way to code the merge operation -- not because I disagree that this is a valid Xalan issue, but because I really think folks need to learn how to write stylesheets that don't rely so heavily on variables.
