SSDN - XSL Efficiency tips

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Conferences

	Stylus Studio Feature Requests (1192)
	Stylus Studio Technical Forum (14621)
	Stylus Studio - Registrar en o... (1)
	Stylus Studio - Registrar en o... (2)
	Can a pipeline send a file by ... (2)
	After Updateing WIN10 to WIN11... (12)
	Where do I add the custom java... (3)
	Where is the Diagram tab? (5)
	Applying XSLT to Word DOCX/XML (2)
	CSV conversion via ConvertToXM... (1)
	Text symbols in SS not same as... (4)
	Exposing xquery as webservice ... (6)
	Syntax Identifier (2)
	Saving a Converted XML as an X... (5)
	Output document cannot be pars... (4)
	Archiving output from conversi... (1)
	EDIFACT guideline from Stylus ... (3)
	CSV file putting all the data ... (5)
	Can't install Home version 64b... (5)
	presale - Can I covers this sc... (5)
	Problem with UNB (5)
	Splitting EDIFACT files pipeli... (4)
	[1-20] [21-40] [41-60] Next
	Website Feedback (249)
	XSLT Help and Discussion (7625)
	XQuery Help and Discussion (2017)
	Stylus Studio FAQs (159)
	Stylus Studio Code Samples & Utilities (364)
	Stylus Studio Announcements (113)

Topic

Richard Potts

Subject: XSL Efficiency tips
Author: Richard Potts
Date: 19 Jul 2007 06:15 AM

I've got a number of XSLTs that I've got integrated into a batch processing application (I'm processing about 50,000 files at a go at the moment and this is increasing). I'm looking to make my XSLT as efficient as possible to reduce processing time.. So are there any general efficiency tips I can review (I couldn't find any)?

I've used the profiler and can see my biggest 'expense' is 'looking up' data in external files e.g.

<xsl:variable name="Name">
<xsl:value-of select="document('filename.xml')/GDX/DATA_IDENTIFIERS/DID[NUMBER = $PIDId]/NAME"/>
</xsl:variable>

Any tips on reducing this 'external file lookup time' or any other 'go faster' tips?

(Deleted User)

Subject: XSL Efficiency tips
Author: (Deleted User)
Date: 19 Jul 2007 08:13 AM

Hi Richard,
I guess you are invoking that part of the code multiple times (each time looking for a different $pid); in thic case, you could use xsl:key to index the content of the file and quickly pick the right name given the pid.

Hope this helps,
Alberto

Richard Potts

Subject: XSL Efficiency tips
Author: Richard Potts
Date: 19 Jul 2007 12:39 PM

Thanks for the 'clue' I've not used 'keys' before. After reading a bit this is my best shot at a 'test' file, but it complains about"The attribute 'match' is already used in element xsl:key"??

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:key match="PIDName" match="/GDX/DATA_IDENTIFIERS/DID/NAME" use="NUMBER"></xsl:key>
<xsl:template match="/">
<xsl:variable name="PIDId">DD00</xsl:variable>

<xsl:for-each select="document('gdx.xml')">
<xsl:variable name="Name">
<xsl:value-of select="key ('PIDName',$PIDId)"></xsl:value-of>
</xsl:variable>
<xsl:value-of select="$Name"></xsl:value-of>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>

Richard Potts

Subject: XSL Efficiency tips
Author: Richard Potts
Date: 20 Jul 2007 08:16 AM

Have figured it out - had a typo in the <xsl:key> line...
Just need to experiment now to see if there is an improvement.

Thanks.

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:key name="PIDName" match="/GDX/DATA_IDENTIFIERS/DID" use="NUMBER"></xsl:key>
<xsl:template match="/">
<xsl:variable name="PIDId">0xDD00</xsl:variable>

<xsl:for-each select="document('gdx.xml')">
<xsl:variable name="Name">
<xsl:value-of select="key ('PIDName',$PIDId)/NAME"></xsl:value-of>
</xsl:variable>
<xsl:value-of select="$Name"></xsl:value-of>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>

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 to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

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-2016 All Rights Reserved.