Improve upon Admin Tool Algorithms
dyiop opened this issue · 0 comments
dyiop commented
There are a few additonal features in the Admin Tool, which would potentially make it slow for larger graphs. This will be an ongoing process but to start, I can see these fixes to make:
- getting children for grid view (inUpdateGridNodes)
- cache children of node?
- build local copy of graph heiracrhly
- add limit later - we could have millions of nodes.
- issue will be when something updates
- for now just rest all of cache but soon you could find a way to only reset the effected nodes
- build local copy of graph heiracrhly
- cache children of node?
- getActiveNodes currently O(n^2)
- Traverse through all nodes from an active PC. Return visited nodes
- whole Active PC’s thing
- Is this feature necessary. It is adding significant complications to various parts of the code base.
- It will also be an issue when we modularize core and admin tool functionality, since the “active pc” logic is currently in the core library wrapper
- to full json?
- can we just regular function with algorithm to retreive only parents?