Saxon

I'm running a test. What's happening is this:

• There is a single TimingTraceListener with a single dataset for the metrics shared by all the transformations
• At the end of each transformation, TimingTraceListener.close() is called, and this triggers execution of the stylesheet to generate the profile report.
• The metrics are then used to build an XML document which forms the input to the transformation. The metrics are not cleared after being displayed, so the successive displays (one for each transformation) show cumulative results
• The HTML reports are all appended to the single output file; the browser is quite happy to display several HTML documents concatenated into a single file.

I propose to make only modest changes:

(a) The metrics should be reset after being displayed, so each transformation produces a table of results that relate to that transformation only

(b) The header information in the output report should enable the transformations to be distinguished.

I've implemented this; the changes were a bit more extensive. In particular, it's not enough to clear the metrics after display, because there is actually a stack of transformations invoked using fn:transform(), not a linear sequence; so we maintain a stack of metric collections for each active transformation. The formatting stylesheet has been adapted to show the URI of the stylesheet, the start time, and an indication of whether it's an fn:transform() transformation. Note that the tables are in order of stylesheet completion, so the outermost stylesheet is displayed last.

This is done on the 12.x branch and I'm not proposing to retrofit it to 11.x.