|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XSL Transformation overhead
Thanks, prs -----Original Message----- From: Pieter Reint Siegers Kort [mailto:pieter.siegers@xxxxxxxxxxx] Sent: Thursday, January 13, 2005 11:32 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: RE: XSL Transformation overhead Hi Rajan, in addition to all the posts, if your xslt stylesheets do not change, then you will want to preload them and add them to some type of cache, this would eliminate multiple parsing and loading penalties. Also, starting up Java has some costs but only the first time. 60,000 faxes per hour of each 50KB does require some hardware, and I think it would be appropiate to have each transformation conclude as this frees up resources. Like MK and other say, your next step should be running and monitoring the system and if necessary determine performance bottlenecks - that way you'll get to the specific system components that you should change in one way or another. When you do that you'll be able to come up with more specific questions. Good luck! HTH, <prs/> -----Original Message----- From: Bhaskar, Rajan [mailto:RBhaskar@xxxxxxx] Sent: Wednesday, January 12, 2005 2:14 PM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: XSL Transformation overhead Hi, I want to know which if xsl transformation of xml or xml parsing would provide better performance in increased load. Our system requires around 15TPS and everyday during the peak 2 hours a volume of 120000 faxes needs to sent/received. the xml size is app. 50KB. Any thoughts? Thanks, Rajan
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








