Handling smaller trees representing branches of the big tree
I have a very big tree. Is it problematic if instead of keeping that big tree my program concurrently handles many smaller trees representing branches of that big tree?
Knowing I wouldn’t decide where the branches are cut from to make this the most efficiently but this would be imposed on me (so I’d end up dealing with many smaller trees of unequal size pointing to each other). The goal is to handle the capacity of the same branches (not copies of their contents nor links) to concurently exist at different locations in the tree.
algorithm data-structures tree branch
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
add a comment |
I have a very big tree. Is it problematic if instead of keeping that big tree my program concurrently handles many smaller trees representing branches of that big tree?
Knowing I wouldn’t decide where the branches are cut from to make this the most efficiently but this would be imposed on me (so I’d end up dealing with many smaller trees of unequal size pointing to each other). The goal is to handle the capacity of the same branches (not copies of their contents nor links) to concurently exist at different locations in the tree.
algorithm data-structures tree branch
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
1
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20
add a comment |
I have a very big tree. Is it problematic if instead of keeping that big tree my program concurrently handles many smaller trees representing branches of that big tree?
Knowing I wouldn’t decide where the branches are cut from to make this the most efficiently but this would be imposed on me (so I’d end up dealing with many smaller trees of unequal size pointing to each other). The goal is to handle the capacity of the same branches (not copies of their contents nor links) to concurently exist at different locations in the tree.
algorithm data-structures tree branch
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
I have a very big tree. Is it problematic if instead of keeping that big tree my program concurrently handles many smaller trees representing branches of that big tree?
Knowing I wouldn’t decide where the branches are cut from to make this the most efficiently but this would be imposed on me (so I’d end up dealing with many smaller trees of unequal size pointing to each other). The goal is to handle the capacity of the same branches (not copies of their contents nor links) to concurently exist at different locations in the tree.
algorithm data-structures tree branch
algorithm data-structures tree branch
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
asked Nov 13 '18 at 1:15
AnskulainenAnskulainen
377
377
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
1
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20
add a comment |
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
1
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
1
1
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20
add a comment |
0
active
oldest
votes
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%2f53272365%2fhandling-smaller-trees-representing-branches-of-the-big-tree%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53272365%2fhandling-smaller-trees-representing-branches-of-the-big-tree%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
Are you thinking of a recursive divide and conquer algorithm? If so, then that is not at all problematic - quite the opposite! Otherwise, could you maybe add some code / pseudo code that demonstrates what you are trying to do?
– runcoderun
Nov 13 '18 at 8:01
1
@runcoderun Branches would be iterated upon by a human user, nodes added or deleted, children re-ordered under their parent, entire branches moved, searches be made for information contained in nodes on the tree, computations made from data stored at nodes distributed across the tree, etc. Nodes would consist of a set of data (a small table perhaps). I´m trying to figure out what data structure to use so that some branches can concurrently be present at several locations in the tree all the while maximising performance/efficiency/simplicity for the aforementioned routine manipulations.
– Anskulainen
Nov 13 '18 at 8:20