Feature request: Improve UX when loading dataspaces

[akphi]

Similar requests

• I have searched and found no existing similar requests

How are you using Studio?

No response

What problems are you trying to solve?

Loading dataspaces have some problems:

1. It takes a while to build a dataspace, since we want to build the full graph to render diagrams, as well as preparing the execution context, etc. This sometimes can take a long time to load dataspaces and sometimes even cause Chrome to crash since building the full graph can take up a lot of memory, also due to reusing the graph here and there, we end up in a situations where we mess up state resetting, causing memory leaks.
2. We don't communicate about this very well, the UI now only shows loading indicator without saying much about the status of loading the graph, this could help

Describe the solution you would like to see implemented

• Give more feedback while loading the graph
• Do not build graph anymore when loading query setup and showing dataspaces - improve Legend Query and Legend Taxonomy performance #1295 - The idea here is we could have an endpoint in engine to build acquire just the necessary material to build diagram/dataspace. For diagram, for example, we could do something like in Pure IDE light to only have necessary material, which does not even comply to the protocol of Diagram. @pierredebelen proposed that we could have build artifacts for dataspace, this will do analytics like test coverage, rendering diagram info (that is not protocol model, but an intermediate representation or SVG) - fix problem with dataspace analytics endpoint legend-engine#807 , Cleanup mapping analytics API and allow searching for queries by version legend-engine#789 , and make dataspace and diagram API more robust and backward-compatible legend-engine#764
• Check RFC: Address graph building performance and memory usage #927 and Bug: Investigate potential memory issue with Legend Query and Legend Taxonomy #1092 again after this

Describe alternatives you have considered

This ties to what we need to do in #927

Documentation, Design, Adoption, Migration Strategy

No response

Contribution

• I would like to work on this feature