XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1123)
+ Stylus Studio Technical Forum (13809)
+ Website Feedback (243)
- XSLT Help and Discussion (7447)
-> + Can't use (or see) XSLT or WYS... (3)
-> + Delete the xsi:nil attribute ... (2)
-> + FOTY0012: Cannot get the typed... (5)
-> + XSLT Mapper - Two way xslt map... (2)
-> + EDI (5)
-> + XSL Test for lack of XML eleme... (4)
-> + Trouble Calling a java functio... (4)
-> + How to generate EDI 997 (2)
-> + followup on tokenize with /r (5)
-> + tokenize a string with \r (4)
-> + How to convert XML to XLS file... (2)
-> - How to convert XML to XLS file... (1)
-> + how to pass value to xsl for t... (3)
-> + entity expansion liimit exceed... (4)
-> + Creating XSLT Stylesheet (2)
-> + Create XSLT from XSD (2)
-> + How to remove nodes from xml b... (4)
-> + Highlighting text in XSL file (4)
-> - XSLT to Excel, predefine cell ... (1)
-> + CSaxon8Driver issue...time out (2)
-- [1-20] [21-40] [41-60] Next
+ XQuery Help and Discussion (1861)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (361)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Julio de la VegaSubject: XSLT vs XQuery
Author: Julio de la Vega
Date: 15 Oct 2007 11:03 AM
Originally Posted: 15 Oct 2007 11:02 AM
Hi *,

I need to transform an xml input into xml output. I have been told that I can use XSLT or XQuery. Could anybody tell me which lenguage has a better performance?

Thanks in advance

Regards

Posttop
Minollo I.Subject: XSLT vs XQuery
Author: Minollo I.
Date: 15 Oct 2007 11:21 AM
Rarely you tie languages to performace. You usually talk of performance about implementations of a language; and even in that case, often implementations are tuned to perform particularly well in a number of usecases, but they may perform less well in other contexts. And often performance is also tightly couple to how "well" you use a specific language (even if a good implementations in some cases are able to cope even with badly written programs).

That said, in our experience it is easier to optimize XQuery execution than XSLT; and that's particularly true when dealing with relational databases, or large XML documents.

As biased as our judgement can be, DataDirect XQuery (http://www.xquery.com) is usually perceived by our users as an extremely scalable and performant XQuery implementation. You can find more details about that on the website.

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.