objectionary / objectionary/lints
`atom-in-atom` XSL transformation exceeds 100ms threshold on large XMIR files
@volodya-lombrozo is already working on this.
Since Jun 24, 2026.
- Dominant language
- Java
- Stars
- 14
- Forks
- 39
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 90
Description
I'm getting performance warnings when running lints against eo-runtime:
[WARNING] XSL transformation 'atom-in-atom' took 120ms, whereas threshold is 100ms
What happens: The selector //o[eo:atom(.) and o[eo:atom(.)]] calls eo:atom(.) on every <o> in the document and then again on each of their children. eo:atom(.) = exists($o/o[@name=$eo:lambda]) performs a child element lookup each time. The effective cost is O(n × degree), which on large XMIR files with many objects and children exceeds the threshold.
What should happen: The transformation completes within the 100ms threshold for typical XMIR files.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.