Some XSLT processors (perhaps most) will have problems transforming a
300Mbyte XML document, but 300Kbytes should be a doddle.
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Jacquo Johnson [mailto:genxgeek(_at_)gmail(_dot_)com]
Sent: 07 August 2005 17:57
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] XML source size vs . XSLT performance
I have a perl application that calls two
stored procs, each returning multiple result sets. Currently I
concatenate the multiple result sets from each stored proc into one
xml document. Worst case the xml document can get up to 300k in size
(when both results from each stored proc are concatenated).
Currently, I'm using Xalan to run a stylesheet on that document but
I'm wondering if 300k is too big of an xml document for Xalan to
transform. So, my question is should I break it up into two parts
(two xml documents one from each stored proc call) or are there any
limitations with xslt and the size of an xml source document in
relation to performance?
Thanks.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--