You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interacting with Eunice analysis in its web page, navigation between items unnecessarily re-counts dependencies. The counts of dependencies will only be different when the YAML that represents items and their dependencies is edited. This unnecessary re-counting has noticeable affect on performance.
The counting of dependencies and visualisation could be separated from each other. Then when an item is selected by the user, re-counting can be avoided and just the necessary graphical rendering performed.
By default Eunice's interactive web page loads with an aggregate of all stack counts, so will have already counted for sub-stacks; however, this information is not currently retained as a single graph for re-use.
The text was updated successfully, but these errors were encountered:
grahamdyson
changed the title
item navigation and dependency lists, with the same YAML, re-builds model
item navigation and dependency listing re-counts dependencies
Jul 22, 2020
When interacting with Eunice analysis in its web page, navigation between items unnecessarily re-counts dependencies. The counts of dependencies will only be different when the YAML that represents items and their dependencies is edited. This unnecessary re-counting has noticeable affect on performance.
The counting of dependencies and visualisation could be separated from each other. Then when an item is selected by the user, re-counting can be avoided and just the necessary graphical rendering performed.
By default Eunice's interactive web page loads with an aggregate of all stack counts, so will have already counted for sub-stacks; however, this information is not currently retained as a single graph for re-use.
The text was updated successfully, but these errors were encountered: