Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve upon Admin Tool Algorithms #23

Open
4 tasks
dyiop opened this issue May 18, 2022 · 0 comments
Open
4 tasks

Improve upon Admin Tool Algorithms #23

dyiop opened this issue May 18, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@dyiop
Copy link
Contributor

dyiop commented May 18, 2022

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
  • 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?
@dyiop dyiop added the enhancement New feature or request label May 18, 2022
@dyiop dyiop self-assigned this May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant