Hi Andrew. I'm a bit confused about your report.
> and after XSLTC, it is about twice as slow as XT.
So, you are saying that in your experements XSLTC seems to be slower that
the interpreted Xalan? This would certainly be a surprise! How are you
measuring?
As for memory usage, in most cases it should be better (though the real
point is to reduce object management, rather than just raw memory).
However, in the case of using Xalan with a DOM, memory usage may increase
somewhat from earlier non-DTM versions. This is because Xalan has to wrap
the DOM tree with a DTM mapping, where before it could work directly from
the DOM. This was a design choice we made. The verdict is not yet in if
it was the right one.
Also, there is a problem with Result Tree Fragments that Joe is currently
working on, that will greatly effect memory usage in some cases.
-scott
[EMAIL PROTECTED]
calate.com To: [EMAIL PROTECTED]
cc: (bcc: Scott Boag/CAM/Lotus)
01/11/2002 Subject: Why Xalan uses a lot of
memory?
05:58 PM
I thought DTM will reduce the memory usage.
Compare to XT, Xalan J 2.2.D14 uses about same amount of memory.
and after XSLTC, it is about twice as slow as XT.
I am new to this group, anything I missed here?
Thanks!
Andrew Duan
