XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » Why Is The Saxon Processor So Slow?
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - UV Kit (1)
-> - Preview PDF as HTML? (1)
-> + ArrayIndexOutOfBoundsException... (3)
-> + WSCC to KML transform help (5)
-> + Using XSV 3.1-1 as an external... (2)
-> + Cannot debug stylesheet (2)
-> + Error installing Stylus Studio... (3)
-> - Windows XP "not responding" er... (1)
-> - Windows XP "not responding" er... (1)
-> + HTML to XSL (2)
-> + Run Stylus studio from command... (2)
-> + Setting Context for XPath Quer... (5)
-> + Batch process to check well-fo... (9)
-> + WSDL validator? (8)
-> - How to be still using Old Jars (1)
-> - Install Stylus Studio on anoth... (1)
-> + Install Stylus Studio on anoth... (3)
-> + How to validate via catalog lo... (4)
-> + New Installation Upgrade Issue... (4)
-> - Freelance Project - Mapping di... (1)
-> + Converting from Edifact to SQL... (3)
-> + converting data file to xml us... (2)
-> + have serious problem with Styl... (2)
-> + ddtek:sql-delete (3)
-> + Web Service Call with Axis: No... (3)
-> + Entity gets replaced when inde... (2)
-> + EDIFACT import error (3)
-> + (401) forbidden error (8)
-> + Error when data type not speci... (2)
-> - Globally delete duplicates of ... (1)
-> + Validation too slow!!!! (4)
-> + Define a complex type with mul... (2)
-> + XML Playlists (2)
-> - Create SOA Web Service with me... (1)
-> + Spell checking?? (2)
-> - saxon 9 linebreak in text mode (1)
-> + Apache FOP gets NoClassDefFoun... (3)
-> + Nillable Decimal (4)
-> + Transform XML to AS400 Databas... (4)
-> + xs3p vs xsDoc (3)
-> + Update Installation Problem (11)
-> + Java Heap error and -Xmx param (5)
-> + 2007 Pro won't run XSL files c... (3)
-> + access to multiples databases ... (6)
-> + License Authentication Failed (2)
-> + XSLT Mapper: How to aggregate ... (2)
-> + Why my WYSIWYG tab disappeared... (3)
-> + Flat File (From mainframe COBO... (9)
-> + X12 Validation (5)
-> + Schema replacement in Microsof... (2)
-> + [OT] XML fragment - error expl... (3)
-> + Re-using a simple type definit... (2)
-> + What is "Java bult-in" XSLT Pr... (2)
-> + Error when generating .NET cod... (6)
-> + options for sum(function) - to... (2)
-> + [OT] XSD - is this valid XML o... (2)
-> + Multiple page sequences (2)
-> + License disabled (3)
-> + EDIFACT to XML with multiple Q... (5)
-> + Viewing Web Service Call http ... (2)
-> - keyref handling by different p... (1)
-> + Running transform in SS UI com... (9)
-> + Mapping from one schema to ano... (3)
-> - Using document() to lookup fro... (1)
-> + Can not open a xml file in IE ... (2)
-> + Stylus Studio detected a chang... (3)
-> + Customer Support for Stylus St... (2)
-> + WebService Call is not working... (3)
-> + Activation Problem (2)
-> + Activating Stylus Studio 2008 (3)
-> + Cannot use UNC paths, get save... (22)
-> + DB to XML Data Source not avai... (3)
-> + Stylus Studio 2008 Installatio... (16)
-> - SQL Server 2005 xml datatype -... (1)
-> + XML Reporting: linking to sect... (4)
-> + Merge an external xml with inp... (4)
-> + Stylus Closing abruptly (4)
-> + Best approach for generating X... (2)
-> + Problem with Java call (5)
-> + Changing the top margin (2)
-> + Generating a Web Service Call (2)
-> + import xml into excel using V... (2)
-> + FOP producing NoSuchMethodErro... (6)
-> + Reporting Errors (2)
-> + Doc/Literal Wrapped (2)
-> + Need image to render at higher... (3)
-> + HTML to xml wizard on thousand... (2)
-> + Doc/Literal and SOAP Header/Bo... (2)
-> - Help with settping up MS Acces... (1)
-> + WSDL - A Well Defined Service (7)
-> + XML to XML Mapping - Combining... (2)
-> + CData Question (3)
-> + mySQL DB Connection (11)
-> + XPath documentation confusion (2)
-> + Extra block/CR generated (6)
-> + Apache FOP (2)
-> + Inserting Java Script (2)
-> + Convert EDIFACT to X12 or vice... (6)
-> + XSD: Restricting an attribute ... (2)
-> + Creating dynamically named ele... (2)
-- Previous [1201-1220] [1221-1240] [1241-1260] 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  
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 29 Sep 2007 06:57 AM
This is something that I've noticed for quite awhile now-- Saxon 8.9.0.3 is absolutely the slowest XSLT processor out of all choices in Stylus Studio. It takes significantly longer to complete a transformation than all the others.

For an XSLT 1.0 transformation, it took 1.6 seconds to complete.

For comparison, here are results for some of the others:

Built-in: 16ms
Java Built-in: 391ms
.NET Transform: 63ms
.NET Compiled Transform: 141ms
Postnext
Minollo I.Subject: Why Is The Saxon Processor So Slow?
Author: Minollo I.
Date: 29 Sep 2007 08:39 AM
That's because Saxon is hooked in Stylus Studio to provide debugging and backmapping information; by no means is Saxon slow; what you are experiencing is a side effect of its tighter integration in the Stylus Studio debugging framework.

We have improved things significantly in recent maintenance packages, and even more in the coming version this fall; what Stylus Studio version/build (Help > About) are you running?
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 29 Sep 2007 08:49 AM
My current version installed is 2007 R2 Enterprise 894m.

Note that I have observed this same behavior with every R2 2007 Enterprise release I have ever had installed. .NET XslTransform and built-in both support debugging, correct? They are significantly faster in execution though. Hmm.
Postnext
(Deleted User) Subject: Why Is The Saxon Processor So Slow?
Author: (Deleted User)
Date: 01 Oct 2007 10:42 AM
Hi Jamil,
could you share your XSLT with us? Send it to stylus-field-report@progress.com and we'll check if it follows code paths that are not yet optimized.

Thanks,
Alberto
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 01 Oct 2007 06:40 PM
I just emailed a ZIP file containing my Stylus Studio project files to the email address specified. It is a small project, but it demonstrates what I have described.

Thanks.
Postnext
(Deleted User) Subject: Why Is The Saxon Processor So Slow?
Author: (Deleted User)
Date: 03 Oct 2007 10:39 AM
Hi Jamil,
thank you for sharing your project with us.
I tried running the ValidatorToHtml.xsl file on my computer, and these are the results:

Processor Min Max
Builtin 20 ms 60 ms
Saxon 219 ms 431 ms
Java builtin 181 ms 371 ms
.NET 101 ms 180 ms

My numbers seems comparable to yours, but the Saxon ones; I have tried with both JVM 1.5 and 1.6. Which one are you using?

Alberto
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 03 Oct 2007 05:48 PM
I am running 1.6 on a decently classed machine (CPU power, memory, etc).

Saxon is a little faster if I set the execution mode to basic. The transformation executes in 1.2 seconds then (I just ran it). This is the first time executing it after starting Stylus Studio. All of my timings have been the first execution for each processor.
Postnext
(Deleted User) Subject: Why Is The Saxon Processor So Slow?
Author: (Deleted User)
Date: 04 Oct 2007 09:36 AM
Hi Jamil,
you should discard the timing of the first execution after Stylus starts; there is a certain amount of one-time operations (initializing the JVM, loading the Saxon JARs) that is not part of the XSLT processing. You should get lower numbers for any other subsequent execution.

Alberto
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 04 Oct 2007 10:07 AM
That explains it.

Thanks.
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 05 Oct 2007 10:21 AM
>you should discard the timing
>of the first execution after
>Stylus starts; there is a
>certain amount of one-time
>operations (initializing the
>JVM, loading the Saxon JARs)
>that is not part of the XSLT
>processing. You should get
>lower numbers for any other
>subsequent execution.

Thinking about this a little more, would it make sense to do all this setup in a separate thread during startup? It's around one second of initialization that could occur during startup, correct? This way, I receive the correct timings during transformation the first time I execute.

Should I post this under feature request?
Postnext
(Deleted User) Subject: Why Is The Saxon Processor So Slow?
Author: (Deleted User)
Date: 05 Oct 2007 12:03 PM
Hi Jamil,
unfortunately it's not possible to move this initialization phase to the startup of Stylus, as the JVM could crash if the user specifies the wrong options (and with the JVM crashing at startup the user could not access the option page to fix the parameters). Also, we would get the complaints of those users using Stylus to run only .NET processors....

Could you elaborate why the first execution timing worries you so much?

Thanks,
Alberto
Postnext
Jamil TaylorSubject: Why Is The Saxon Processor So Slow?
Author: Jamil Taylor
Date: 05 Oct 2007 12:29 PM
Until this thread, I was not aware that I should ignore the first execution of a Saxon-based XSLT transformation. If I throw away the results of the first execution, then Saxon is no longer the slowest processor.

However, if this initialization is required (for whatever reasons), then I cannot throw away the results of the first execution. Saxon is the slowest processor for XSLT transformations. If the reasons for it being the slowest is the loading of Saxon jars, I do not understand why the loading of jars cannot be done during startup. Loading the jars could crash the JVM? Perhaps I should just avoid Saxon...

I am a .NET developer, and I would not complain about the loading of jars in a completely different thread. Of course, I cannot speak on behalf of all .NET developers, but I would not understand the reason behind those who would complain about it.

If Saxon is the fastest/best/etc, I am not seeing proof of that in this implementation of it. It's really not that big of a deal to me, but it is good for analysis.
Posttop
(Deleted User) Subject: Why Is The Saxon Processor So Slow?
Author: (Deleted User)
Date: 05 Oct 2007 01:23 PM
Hi Jamil,
I think we are talking about different things here; if you want to discover which processor is the fastest, you should know that every benchmark will always discard the first iteration, the fastest and the slowest and then average a certain amount of executions.
As for the JVM crashing, I didn't state that loading Saxon jars crashes the JVM; I said that loading the JVM with certain user-specified options (like "allocate 4Gb of memory") will cause a "panic error" in the JVM that kills Stylus.

Hope this helps,
Alberto
   
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-2016 All Rights Reserved.