Final update,
with 256m allocated to java
and a varient of Michael & Wendell's code:
<xsl:variable name="goodid">
<xsl:for-each select="$id-master">
<xsl:if test="not(key('keys-by-id',
$id))">1</xsl:if>
</xsl:for-each>
</xsl:variable>
my transform ran like a bat out of hell!
THANKS so much!
-----Original Message-----
From: Wolpert, Jake
Sent: Friday, November 21, 2003 11:57 AM
To: 'xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com'
Subject: RE: [xsl] Lookup efficiency in XALAN?
DUH, I forgot to RTFM!
I had assumed that java would use whatever memory I had, WRONG!
When I goose the java memory up to 256m! Xalan moves faster, processed all
my records... But, most important, finally it worked.
I guess I was running out of memory and using a slow/simplistic
lookup method. Now that I have allocated lots of memory... I think it's time
to revisit Michael & Wendell's optimizations.
Thanks to Michael & Wendell & Robert!
-----Original Message-----
From: Dr. Robert Spiske [mailto:spiske(_at_)chemie(_dot_)uni-halle(_dot_)de]
Sent: Friday, November 21, 2003 1:03 AM
To: JWolpert(_at_)shaklee(_dot_)com
Subject: [xsl] Lookup efficiency in XALAN?
Hi!
You don't mention it, but i assume you raised the amount of memory your
Java-VM may use?
There some memory problems which can be resolved with some hints from:
http://xml.apache.org/xalan-j/faq.html#faq-N100B4
good luck
Robert
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list