Skip to content

perf: accelerate no-cache cold compiles - #768

Merged
kvlonge merged 4 commits into
mainfrom
fix/no-cache-closure-index
Sep 21, 2026
Merged

kvlonge merged 4 commits into
mainfrom
fix/no-cache-closure-index

Conversation

@kvlonge

@kvlonge kvlonge commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Why

Fresh-process --no-cache compilation was doing cache-only work and retaining avoidable Python front-end overhead. The previous cold budgets were loose enough to accept the reported 5k/10k regression signal.

Changes

  • Skip cache-only closure and compact-plan construction when caching is disabled.
  • Replace per-reference qualification regexes with one gated scan.
  • Reuse static model metadata and declaration visibility projections.
  • Batch SQL-test header preparation and use faster JSON boundaries with compatibility fallback.
  • Tighten 3k/5k/10k wall guards to 11s/15.5s/29.5s, with RSS and semantic-fingerprint assertions.

Verification

  • Cold fresh-process guards: 3k 8.64s, 5k 12.34s, 10k 23.06s; fingerprints unchanged.
  • 5k cache lifecycle: cold 15.81s, warm 8.32s; leaf, macro, and project-config invalidation passed.
  • Focused regressions: 182 passed; final affected-boundary suite: 170 passed.
  • uv sync --all-extras; make check-ci.
  • Public-repository hygiene scan.
  • Independent review completed; all four findings fixed and verified.

@kvlonge
kvlonge enabled auto-merge (squash) September 21, 2026 10:22
@kvlonge
kvlonge merged commit 794b9dd into main Sep 21, 2026
25 checks passed
@kvlonge
kvlonge deleted the fix/no-cache-closure-index branch September 21, 2026 10:54
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