Skip to content

fix: reduce large-project planning work - #748

Merged
kvlonge merged 1 commit into
mainfrom
perf/planning-state-scaling
Sep 20, 2026
Merged

kvlonge merged 1 commit into
mainfrom
perf/planning-state-scaling

Conversation

@kvlonge

@kvlonge kvlonge commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Why

Large projects paid repeated planning costs that scaled with both model count and SQL-test count. Each selected SQL test rebuilt the same project-wide fixture metadata, complete authoritative fixtures still triggered required-column analysis, and broad Snowflake relation inspection used unnecessarily small serial query chunks.

Changes

  • build and reuse one fixture-planning context per selected test set
  • skip required-column analysis when an inferred fixture already supplies every authoritative column
  • preserve per-test expected-type propagation without mutating shared metadata
  • increase bounded Snowflake bulk column inspection chunks from 200 to 2,000 relations
  • add deterministic work-count guards plus compile-to-plan integration coverage

Verification

  • focused planner, scenario, required-column, and Snowflake tests: 114 passed
  • fixture work-guard and integration tests: 3 passed after test-structure updates
  • make check-ci
  • independent read-only correctness review: no findings

@kvlonge
kvlonge enabled auto-merge (squash) September 20, 2026 05:16
@kvlonge
kvlonge merged commit c553f54 into main Sep 20, 2026
17 checks passed
@kvlonge
kvlonge deleted the perf/planning-state-scaling branch September 20, 2026 05:28
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