> With 2.2D7, the memory footprint is about
> 40% larger
If you feed Xalan a W3C DOM, the memory footprint will indeed be larger.
What we now do is produce a mapping from our DTM (Document Table Model) to
the DOM. By doing this, we don't have to be restricted to using the W3C
interfaces within Xalan, which have proved to be rather inadequate for high
performance processing. Actual processing time should be faster, though we
haven't done much study yet on performance with a DOM configuration.
> and it does not appear to be garbage collecting properly
> (identical code on our end)
Interesting. I'm not aware of any garbage collection problems. You should
post a bug report at http://nagoya.betaversion.org/bugzilla/, providing as
much information as possible to let us reproduce the problem.
-scott
"Rick Bullotta"
<Rick.Bullotta@lighth To: <[EMAIL PROTECTED]>
ammer.com> cc: (bcc: Scott Boag/CAM/Lotus)
Subject: Xalan 2.2 D7 increasing
memory footprint?
07/23/01 11:08 AM
Please respond to
xalan-dev
We have a need to generate an in-memory DOM of nearly 320,000 nodes and
then
apply an XSLT transformation to it (no, there isn't another way,
unfortunately). In Xalan 2.1, it works fine, and the memory footprint,
while significant, is liveable. With 2.2D7, the memory footprint is about
40% larger, and it does not appear to be garbage collecting properly
(identical code on our end), as subsequent request generate an
out-of-memory
error (with Xalan 2.1, repeated requests process without problem).
Any thoughts? Suggestions?
- Rick Bullotta
CTO
Lighthammer Software (www.lighthammer.com)
