perf(editor): Avoid deep watch on execution result data #15304
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
autologie
changed the title
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
mrge reviewed 3 files and found no issues. Review PR in mrge.io.
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
MiloradFilipovic
approved these changes
May 12, 2025
|
✅ All Cypress E2E specs passed |
|
Got released with |
ozcangungor
pushed a commit
to ozcangungor/n8n
that referenced
this pull request
May 25, 2025
etobella
pushed a commit
to etobella/n8n
that referenced
this pull request
May 25, 2025
Alexandero89
pushed a commit
to Alexandero89/n8n
that referenced
this pull request
May 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves canvas performance while executing a workflow that generates many runs by replacing deep watch on execution response with update timestamp.
The comparison below shows the difference in the main thread work.
For testing, I used a workflow that generates ~300 runs of nodes in a loop Loop__wait.json
Related Linear tickets, Github issues, and Community forum posts
Review / Merge checklist
release/backport(if the PR is an urgent fix that needs to be backported)