objectionary / objectionary/lints

`rt-without-atoms` XSL transformation performance issue with large XMIR files

Open
#992 0 comments 0 reactions 1 assignee View on GitHub

@volodya-lombrozo is already working on this.

Since Jun 24, 2026.

bug good-title
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 'rt-without-atoms' took 128ms, whereas threshold is 100ms
[WARNING] XSL transformation 'rt-without-atoms' took 129ms, whereas threshold is 100ms

What happens: The check not(//o[eo:atom(.)]) scans the entire document when no atom is found. eo:atom(.) = exists($o/o[@name=$eo:lambda]) performs a child lookup per element. When the XMIR file has no atoms, every element in the document is visited, making the cost O(n × degree).

What should happen: The transformation completes within the 100ms threshold. An early exit as soon as one atom is found would reduce cost to O(1) in the common case. Alternatively, an xsl:key for lambda-named children would speed up the atom check.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.