[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

XML source size vs . XSLT performance

Subject: XML source size vs . XSLT performance
From: Jacquo Johnson <genxgeek@xxxxxxxxx>
Date: Sun, 7 Aug 2005 10:57:04 -0600
xml vs xslt
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.

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.