Saxon configuration option TimingTraceListener

[michaelmh]

Hi guys,

to take advantage of the simpler timing feature built into Saxon I added a Saxon configuration file to my transformation configuration (Advanced Options), with the following content:

Code: Select all

<configuration edition="PE" xmlns="http://saxon.sf.net/ns/configuration">

  <global traceListener="net.sf.saxon.trace.TimingTraceListener"

    traceListenerOutputFile="/Users/michael/Downloads/profile.html"/>

</configuration>

That works great!

But if I have "Additional XSLT Stylesheets" selected, the profile.html contains only information from the very last XSLT run, apparently because the filename is the same for all invocations, and therefore the last one wins.

Could you please consider to:
A) Add this option directly into the Saxon options
B) Allowing to trace a full transformer pipe, e.g. by allowing some variables in the output filename, like ${cfn}

As always, I would be glad to hear some method how to achieve my request with the product out-of-the-box (version 21)

Best regards,

- Michael

[tavy]

Hi Michael,

Thanks for your feedback.
Unfortunately I don't have a solution for this problem.
Yes, we could add support for variables in the Saxon configuration file, such us ${cfn}, but then that configuration file will be used only from Oxygen. Probably this support should be added directly in Saxon.

Best Regards,
Octavian

[michaelmh]

Hi Octavian,

I follow your argument, but even better would be a direct option in Oxygen's Saxon settings, to handle that automatically.

A checkbox to activate the TimingTraceListener, with a folder selector, and for every XSLT an HTML file of the same name would be written to that folder.

Best regards,

- Michael

[tavy]

Hi Michael,

Yes, this can be a solution, to have an option in Oxygen that will enable the XSLT profiling based on Saxon TimingTraceListener.
I will add an issue for this.

Best Regards,
Octavian