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...
DRay I'm still keen for Sisense to implement dougnewton's suggestion.
I haven't worked on a data model like that for a while, so I haven't had the problem. If I do, I might try HamzaJ's methods to allocate more resources to the display pod. But it feels a bit silly that I need to allocate more memory for drawing a few circles in a tool that efficiently indexes and pivots billions of rows of data.