I have a data model with lots of tables (more than 30). That makes the UI painfully slow, e.g. when editing relationships. I think the reason is that it’s calculating where to place them on the scree...
How do I do "Solution 2: Increase memory limit in model-graphql deployment"? Are there downsides? We might consider making this part of all our Sisense deployments.
I'll try "Solution 1" if I or others get frustrated again. I'm a bit reluctant to make that our "standard" solution for big models, as we'd need to do it across multiple clients, possibly multiple models, and it's more clutter/customisation/documentation/maintenance.
Ideally, I like Doug's idea: a "don't auto-arrange" toggle to simply leave it up to the user to arrange the diagram would take little dev time for you to implement and solves the problem perfectly for me.
Thanks Hamza.