Michael Kay
Michael Kay- Email: mike@saxonica.com
- Registered on: 2012-02-01
- Last connection: 2020-03-27
Issues
- Assigned issues: 21
- Reported issues: 1314
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)
- Non-Conformances (Manager, 2020-02-26)
Activity
2020-04-04
2020-04-03
-
Looking at the `knownBaseUris` table, an entry is added to this table when we compute the base URI of an element node; the value is retained because computing it is potentially expensive. The reason we are computing the base URI is not (... Bug #4507: TinyTree used for assertion checking during schema validation includes excessive Names...Reported by private email: a validation run, which appears to have an assertion defined on the root element node, is consuming excessive memory. Heap analysis shows a large number of redundant NamespaceBinding objects, accounting for a l... -
Running on 9.9, I found that running with byte code generation disabled (--generateByteCode:off) was faster by 8-10%, but made no difference to memory usage.· Commented on issue
The Java profile showed a measurable cost for the HashMap update at XSIAttri... -
Did some further testing on 10.0 and the extra time and memory used relative to 9.9 seems to have been a measurement glitch.· Commented on issue
I found that on both 9.9 and 10.0, the trace() calls in WatchManager are showing up in the Java profile: alth... -
We've been running this through the debugger on .NET, and we found that when using the Microsoft pull parser it is indeed adding a namespace declaration for the default namespace `xmlns="http://www.ahsa.com.au/schema/medicalagreements"` ...· Commented on issue
-
We now have a new schema file and data file to work with, and I have been doing measurements on this. On the Java platform I'm seeing a validation time of around 20s and memory usage about 1100Mb as reported when run from the command lin...· Commented on issue
-
To expand on O'Neil's reply, a SaxonProcessor holds one "schema" in the sense of a coherent set of schema definitions (element definitions, type declarations etc). It's possible to load multiple schema documents, in which case you're val... Saxon/C Help and Discussions: RE: Saxon/C and Windows: several issues with C++ classesHello,
I am using Saxon/C API 1.2.1 on Windows; first of all: big compliment to all Saxon developers, it is really a nice tool and working stable!
But I noticed three minor issues here (which I could handle by myself) and one maybe g...
2020-04-02
-
I've now drilled down a bit using the IDE debugger and JProfiler heap analysis. This is on the Java platform; we'll go on to confirm the results on .NET.
Everything here seems to be working as designed. Because there's an assertion on... Bug #4507: TinyTree used for assertion checking during schema validation includes excessive Names...Reported by private email: a validation run, which appears to have an assertion defined on the root element node, is consuming excessive memory. Heap analysis shows a large number of redundant NamespaceBinding objects, accounting for a l... -
I now have a sample document to work with, containing anonymised data.· Edited issue
Initial observations:
* The root element is `MedicalAgreement`, which has an assertion defined, therefore we are building a tree containing the entire document.... -
Added for the next maintenance release on the 10.0 branch. Feature #4511 (Resolved): Add new method XdmValue.isEmpty()As suggested by Chapman Flack on the saxon-help mailing list, it would be useful to have a method XdmValue.isEmpty().
Also available in: Atom
.