Skip to content

index: three missing lookup indexes made large-repo queries and warm take minutes - #1847

Merged
swapnilpaliwal-sd merged 1 commit into
0.1.9from
fix/graph-lookup-indexes
Oct 1, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
0.1.9from
fix/graph-lookup-indexes

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor

On a large Java repository the first query after indexing took minutes, and the warm step after a build took more than 20 minutes on one core, holding the build lock. Three lookups had no index, so every per-call-site or per-test query scanned the whole table:

  • symbols by id (the stub-site check of the fact export)
  • refs by file and line (the servlet-filter join run on every path and impact query, and by the edit hooks)
  • literals by file and line (the same join's request check)

The index now creates all three. Measured on a repository with 8,619 Java files and 97k symbols:

before after
first path query several minutes 6 s (2.7 s once the facts are cached)
warm step 20+ min 2 min 46 s

The Java cases pass (329 of 329). The indexes take under a second to create and are additive.

…hrough an index

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit b43cebe into 0.1.9 Oct 1, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the fix/graph-lookup-indexes branch October 1, 2026 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant