Skip to content

Improve document_migration_upgrades time complexity to remove O(n^2) - #4626

Open
0HyperCube wants to merge 1 commit into
GraphiteEditor:masterfrom
0HyperCube:migrate-node-perf
Open

0HyperCube wants to merge 1 commit into
GraphiteEditor:masterfrom
0HyperCube:migrate-node-perf

Conversation

@0HyperCube

Copy link
Copy Markdown
Contributor

Working towards #4572.

There is seemingly no need to run the migration code to create layer stacks for each node. It can just be done once per document after all nodes are migrated.

This fixes a significant hang of several seconds when loading saved .graphite with many layers.

@cubic-dev-ai cubic-dev-ai 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.

All reported issues were addressed across 1 file

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread editor/src/messages/portfolio/document_migration.rs
@TrueDoctor

TrueDoctor commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

!build (Run ID 36877002363)

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown
📦 Web Build Complete for 9d5c2ef
https://01344e04.graphite.pages.dev

Wasm: 40.02 MB — JS: 0.46 MB — CSS: 0.09 MB — Fonts: 0.30 MB — Images: 0.09 MB — All Assets: 40.96 MB

This branch has not been deployed

No deployments
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