Skip to content

⚡ Bolt: [performance improvement] Optimize ERD exports with O(1) handle parsing - #676

Closed
seonghobae wants to merge 1 commit into
mainfrom
bolt-perf-handle-parsing-4909398645755318232
Closed

⚡ Bolt: [performance improvement] Optimize ERD exports with O(1) handle parsing#676
seonghobae wants to merge 1 commit into
mainfrom
bolt-perf-handle-parsing-4909398645755318232

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

💡 What:
Added a parseColumnNameFromHandle utility that decodes sanitizeHandleId strings back to their original column names in $O(1)$. Replaced usages of sourceColumnHandleId/targetColumnHandleId inside array scans in export.ts, exportDataDictionary.ts, mermaid.ts, and dbml.ts with upfront $O(1)$ decoding of edge handles. Added comprehensive tests.

🎯 Why:
During ERD exports (DDL, DBML, Dictionary, Mermaid), checking relationships required matching column names against edge handles. The previous implementation called sanitizeHandleId(columnName) on every single column in the schema inside $O(N)$ or $O(E)$ loops, causing massive CPU string-encoding overhead and garbage collection pressure due to generating hex strings for every node in large graphs.

📊 Impact:
Significantly reduces GC pressure and execution time for exporting schemas with thousands of columns by transforming an $O(N \times C)$ string allocation bottleneck into an $O(1)$ lookup and native string comparison.

🔬 Measurement:
Profile generating exports (like DBML or Mermaid) on a large schema and observe the reduction in memory spikes and execution time. All tests run via cd frontend && pnpm run typecheck && pnpm test && pnpm run build continue to pass.


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

Replaced O(N*C) handle string encoding during ERD exports with an
O(1) parseColumnNameFromHandle utility that reverses sanitizeHandleId.
This drastically reduces CPU usage and garbage collection overhead
during export generation.
@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.

import type { IndexRecommendation } from './cardinality';
import type { ForeignKeyEdgeData, TableNodeData } from './convert';
import { sourceColumnHandleId, targetColumnHandleId } from './handleUtils';
import { sourceColumnHandleId, targetColumnHandleId, parseColumnNameFromHandle } from './handleUtils';
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 097e1185-c1dc-4777-8621-af0973953e57

📥 Commits

Reviewing files that changed from the base of the PR and between 4bf3968 and cf85a2a.

📒 Files selected for processing (9)
  • .jules/bolt.md
  • frontend/src/erd/__tests__/coverageEdges.test.ts
  • frontend/src/erd/__tests__/dbml.test.ts
  • frontend/src/erd/dbml.ts
  • frontend/src/erd/export.ts
  • frontend/src/erd/exportDataDictionary.ts
  • frontend/src/erd/handleUtils.test.ts
  • frontend/src/erd/handleUtils.ts
  • frontend/src/erd/mermaid.ts

Comment @coderabbitai help to get the list of available commands.

@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 superseded and obsolete. I am 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.

1 participant