Merge / Diff on the Node-RED flow is very slow
We are working on various ChatBot project using Node-Red to design conversation.
But "team work" on v0.19 is really painfull when making diff on the flow.
In a nutshell it takes about 2 minutes to make the diff !
- The file has 32000 lines
- For about 2595 nodes (with 679 nodes function)
- Everything is split in various tabs or subflow (30-40)
- There is almost 60-80 nodes / tabs it's readable for Node-RED it's not an "over-usage"
Any ideas to speed up the GIT Diff ?
Thanks !
node-red
add a comment |
We are working on various ChatBot project using Node-Red to design conversation.
But "team work" on v0.19 is really painfull when making diff on the flow.
In a nutshell it takes about 2 minutes to make the diff !
- The file has 32000 lines
- For about 2595 nodes (with 679 nodes function)
- Everything is split in various tabs or subflow (30-40)
- There is almost 60-80 nodes / tabs it's readable for Node-RED it's not an "over-usage"
Any ideas to speed up the GIT Diff ?
Thanks !
node-red
add a comment |
We are working on various ChatBot project using Node-Red to design conversation.
But "team work" on v0.19 is really painfull when making diff on the flow.
In a nutshell it takes about 2 minutes to make the diff !
- The file has 32000 lines
- For about 2595 nodes (with 679 nodes function)
- Everything is split in various tabs or subflow (30-40)
- There is almost 60-80 nodes / tabs it's readable for Node-RED it's not an "over-usage"
Any ideas to speed up the GIT Diff ?
Thanks !
node-red
We are working on various ChatBot project using Node-Red to design conversation.
But "team work" on v0.19 is really painfull when making diff on the flow.
In a nutshell it takes about 2 minutes to make the diff !
- The file has 32000 lines
- For about 2595 nodes (with 679 nodes function)
- Everything is split in various tabs or subflow (30-40)
- There is almost 60-80 nodes / tabs it's readable for Node-RED it's not an "over-usage"
Any ideas to speed up the GIT Diff ?
Thanks !
node-red
node-red
asked Nov 23 '18 at 13:40
Jean-Philippe Encausse
77911334
77911334
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The only realistic answer you are going to get here is use a smaller flow.
It will probably be worth bringing this up on the discord or slack where Nick might be able to look at the code and see if it can be improved. But looking at the code it looks like it's just calling git diff
under the covers.
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447786%2fmerge-diff-on-the-node-red-flow-is-very-slow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The only realistic answer you are going to get here is use a smaller flow.
It will probably be worth bringing this up on the discord or slack where Nick might be able to look at the code and see if it can be improved. But looking at the code it looks like it's just calling git diff
under the covers.
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
add a comment |
The only realistic answer you are going to get here is use a smaller flow.
It will probably be worth bringing this up on the discord or slack where Nick might be able to look at the code and see if it can be improved. But looking at the code it looks like it's just calling git diff
under the covers.
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
add a comment |
The only realistic answer you are going to get here is use a smaller flow.
It will probably be worth bringing this up on the discord or slack where Nick might be able to look at the code and see if it can be improved. But looking at the code it looks like it's just calling git diff
under the covers.
The only realistic answer you are going to get here is use a smaller flow.
It will probably be worth bringing this up on the discord or slack where Nick might be able to look at the code and see if it can be improved. But looking at the code it looks like it's just calling git diff
under the covers.
answered Nov 23 '18 at 14:19
hardillb
23.8k63060
23.8k63060
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
add a comment |
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
At first I thought it was too much nodes. But in fact it's only 60 nodes per tab that i really readable. Git Diff on a file is really fast I assume the problem comes from the UI trying to display the diff
– Jean-Philippe Encausse
Nov 23 '18 at 20:53
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
I continue here with Nick discourse.nodered.org/t/…
– Jean-Philippe Encausse
Nov 23 '18 at 21:06
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53447786%2fmerge-diff-on-the-node-red-flow-is-very-slow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown