Skip to content

⚡ Bolt: [performance improvement] Optimize DBML column position calculation to O(1) - #645

Closed
seonghobae wants to merge 1 commit into
mainfrom
bolt-dbml-import-opt-7461202086995374457
Closed

⚡ Bolt: [performance improvement] Optimize DBML column position calculation to O(1)#645
seonghobae wants to merge 1 commit into
mainfrom
bolt-dbml-import-opt-7461202086995374457

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

⚡ Bolt: [performance improvement] DBML parse optimize

Replace O(N^2) inline generator sum(...) for column positions with O(1) dictionary counter col_count_by_oid in DBML parsing logic.

  • 💡 What: O(1) column position counting in backend/app/spec/dbml_import.py
  • 🎯 Why: Calculating sum(1 for c in columns if c["relation_oid"] == oid) + 1 linearly for every new column creates O(N^2) complexity, degrading DBML parsing speeds on large datasets.
  • 📊 Impact: Significantly improves DBML import speed on schemas with many columns.
  • 🔬 Measurement: Verified with pytest --cov=app which maintains full parity.

PR created automatically by Jules for task 7461202086995374457 started by @seonghobae

Replace O(N^2) inline generator `sum(...)` for column positions with O(1) dictionary counter `col_count_by_oid` in DBML parsing logic.

- 💡 What: O(1) column position counting in `backend/app/spec/dbml_import.py`
- 🎯 Why: Calculating `sum(1 for c in columns if c["relation_oid"] == oid) + 1` linearly for every new column creates O(N^2) complexity, degrading DBML parsing speeds on large datasets.
- 📊 Impact: Significantly improves DBML import speed on schemas with many columns.
- 🔬 Measurement: Verified with `pytest --cov=app` which maintains full parity.
Copilot AI review requested due to automatic review settings July 26, 2026 01:53
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves backend DBML import performance by eliminating an O(N²) column-position calculation inside parse_dbml, making DBML parsing scale better for large schemas.

Changes:

  • Replaced per-column linear scans (sum(...)) with an O(1) per-table counter map (col_count_by_oid) when assigning column_position.
  • Added a Bolt performance note documenting the optimization and rationale.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
backend/app/spec/dbml_import.py Uses col_count_by_oid to compute column_position in O(1), preserving 1-based ordering while avoiding repeated scans.
.jules/bolt.md Documents the learning/action for avoiding O(N²) column position computation during DBML parsing.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@opencode-agent opencode-agent Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5576258800035f913d0dfa119fc66a6987f8602a.

  • Head SHA: 5576258800035f913d0dfa119fc66a6987f8602a

  • Workflow run: 30505467541

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: bolt.md"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: bolt.md"]
  R1 --> V1["required checks"]
  Evidence --> S2["Backend: dbml_import.py"]
  S2 --> I2["API and service runtime"]
  I2 --> R2["Review risk: Backend: dbml_import.py"]
  R2 --> V2["backend tests"]
Loading

@opencode-agent

Copy link
Copy Markdown
Contributor

OpenCode Review Overview

  • Head SHA: 5576258800035f913d0dfa119fc66a6987f8602a
  • Workflow run: 30505467541
  • Workflow attempt: 1
  • Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode cannot approve yet because required coverage evidence did not pass.

Review outcome

1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence

  • Problem: The required coverage-evidence job result was failure, so OpenCode cannot establish approval sufficiency for this head.

  • Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.

  • Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports success with required evidence or explicit no-source not-applicable evidence.

  • Regression test: Keep the approval branch checking needs.coverage-evidence.result == success before posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present.

  • Result: REQUEST_CHANGES

  • Reason: coverage-evidence result was failure, so required test/docstring evidence was not proven for current head 5576258800035f913d0dfa119fc66a6987f8602a.

  • Head SHA: 5576258800035f913d0dfa119fc66a6987f8602a

  • Workflow run: 30505467541

  • Workflow attempt: 1

Coverage evidence

Coverage Decision

  • Result: FAIL
  • Test evidence: not proven passing
  • Docstring evidence: not proven passing when configured
  • Failure count: 1

Changed-File Evidence Map

flowchart LR
  PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
  Evidence --> S1["Changed file: bolt.md"]
  S1 --> I1["repository behavior"]
  I1 --> R1["Review risk: Changed file: bolt.md"]
  R1 --> V1["required checks"]
  Evidence --> S2["Backend: dbml_import.py"]
  S2 --> I2["API and service runtime"]
  I2 --> R2["Review risk: Backend: dbml_import.py"]
  R2 --> V2["backend tests"]
Loading

@seonghobae

Copy link
Copy Markdown
Collaborator Author

Closed as superseded/duplicate agent perf micro-optimization; main already has comparable Bolt export/render opts (#561/#538). Commercial-baseline drain: not uniquely required.

@seonghobae seonghobae closed this Jul 31, 2026
@google-labs-jules

Copy link
Copy Markdown

Closed as superseded/duplicate agent perf micro-optimization; main already has comparable Bolt export/render opts (#561/#538). Commercial-baseline drain: not uniquely required.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

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.

2 participants