Michael Kay
Michael Kay- Email: mike@saxonica.com
- Registered on: 2012-02-01
- Last connection: 2019-10-20
Issues
- Assigned issues: 20
- Reported issues: 1274
Projects
- Saxon (Manager, Developer, Reporter, 2012-02-06)
- Saxon-CE (Manager, Developer, 2012-02-01)
- Saxon/C (Manager, Reporter, 2016-02-24)
- Saxon-JS (Manager, 2016-07-28)
- W3C QT Specifications (Manager, 2019-05-16)
Activity
2019-10-20
-
If we force the predicates to be in the right order, and force promotion to global to happen before loop-lifting, then the first thing that prevents this expression being promited to global is that it is inside a branch of a conditional.... Bug #4340: Performance degraded after moving from Saxon 8.9 to 9.8.0.15 (use case Enterprise cons...Customer upgraded to the latest version of our product which uses Saxon 9.8.0.15 EE.
They came from an older version which used Saxon 8.9.0.14.
They process thousands of documents per day with hundreds of XSLs.
For two use cases (see ... -
I am now studying the optimization of the Relate template, and in particular the filter expression supplied as argument to the `distinct-values()` call, by isolating it into a free-standing stylesheet.· Commented on issue
First observation: the four pred... -
I have committed a patch which hopefully fixes this issue by making the exception that results from StackOverflow non-recoverable when it occurs during pattern matching. Bug #4342 (In Progress): Sporadic spikes in XSL processing time due to internal loopingStylesheet sporadically takes many minutes vs some seconds to run.
Inside the debugger this can be enforced (see steps below).
Given the XSL output warnings like "Too many nested template or function calls. The stylesheet may be lo... -
You mention the warning message "Too many nested template or function calls. The stylesheet may be looping." I haven't seen that message either in my own runs, or in your video, so I'm not sure of its relevance.· Commented on issue
What I do see in the v... -
I have not been able to reproduce this; it runs fine for me with or without debugging enabled.· Commented on issue
However, I have been running under IntelliJ rather than Eclipse. Our normal support policy is that we don't create custom software environm... -
-
I guess there's a workaround of using the XQuery API instead? Bug #4351: set_parameter failing under PyXPathProcessorReported by user in the forum post:
https://saxonica.plan.io/boards/4/topics/7621
I ran the same sample python script under linux with gdb command:
~~~
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x00007fff...
2019-10-19
-
It seems this stack was a rather hastily conceived solution to the problem of how to present aggregated timing data for recursive calls. It seems to be used only to detect that a call is recursive. This could have been done equally well ... Bug #4350: TimingTraceListener (-TP option) has a built-in limit of 1500 on the number of stack f...The TimingTraceListener fails with an ArrayIndexOutOfBounds exception if the number of nested template/function calls exceeds 1500.
-
By the time we get to the stage of global variable extraction, the expression is
~~~
if (exists($RelatedKeys))
then (
let $qq:v3 := data(first($RelatedKeys))
return
(let $qq:v2 := data(($RelationshipExclusions/child... Bug #4340: Performance degraded after moving from Saxon 8.9 to 9.8.0.15 (use case Enterprise cons...Customer upgraded to the latest version of our product which uses Saxon 9.8.0.15 EE.
They came from an older version which used Saxon 8.9.0.14.
They process thousands of documents per day with hundreds of XSLs.
For two use cases (see ... -
We've got an expression of the form `$E/*[P1]{P2][P3][P4]` where `$E` is a global variable reference and P1 has no dependencies other than the context item and other global data, and we would like to see `$E1/*[P1]` promoted to a global ...· Commented on issue
Also available in: Atom
.