Oxygen XML Editor
The Premier All-In-One XML Editing Suite
Oxygen XML Author
Single-Source XML Authoring and Multi-Channel Publishing
Oxygen XML Developer
The Required Tools for Designing XML Schemas and Transformation Pipelines
Oxygen JSON Editor
The Perfect Tool to Simplify Your JSON Editing Experience
Oxygen Publishing Engine
The Complete DITA Publishing Solution for WebHelp and PDF Output
Oxygen PDF Chemistry
Chemistry Converts HTML and XML to PDF Using CSS
Oxygen XML WebHelp
Publish DITA and DocBook Content to WebHelp Output
Oxygen Styles Basket
Customize the Look and Feel of Your PDF and WebHelp Output
Oxygen XML Web Author
Engage Your Whole Organization In Content Creation
Oxygen Content Fusion
The Web-based Collaboration Platform to Craft Tomorrow's Content
Oxygen Feedback
Modern Commenting Platform
Cloud
Enterprise
Oxygen AI Positron
Enhance Your Productivity with the Power of AI
Oxygen Scripting
Automate and Run Oxygen Utilities from the Command-Line Interface
Oxygen SDK
Specifically designed for application developers and integrators
Shop
Pricing and licensing for businesses, Academic and individuals
Whether you are trying to identify a performance issue that is causing your production XSLT transformation to not meet customer expectations, or you are trying to proactively identify issues prior to deploying your XSLT transformation, using the XSLT profiler feature is essential to helping you save time and ultimately ensure a better performing, more scalable XSLT transformation.
The profiling is available for the XSLT processors that are bundled with Oxygen (Saxon 6.5.5, Saxon EE, and Xalan 2.7.1). This allows you to profile XSLT 1.0, 2.0, or 3.0 stylesheets.
Using the Invocation Tree view, also known as a call tree, you can examine how style instructions are processed in a top down manner. The profiling result shows the duration time for each of the style instructions (including the time needed for its child instructions and, when an instruction is expanded, how the instruction time is composed from the child instruction times).
Using the profiler Hotspots view, you can immediately detect the time the processor spent on each instruction. The hotspot displays the inherent time of the instruction (the total time processing that instruction, minus the time processing its child instructions). When a hotspot is expanded, you can see all the different paths that instructions were called from (a reverse invocation tree), the number of invocations, the instruction time on that path, and the percentage that path contributed to the instruction's total execution time.