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 screen.
I’d like to request an alternative, crude interface that doesn’t slow down for lots of tables. Or make it work for lots of tables – e.g. do the positioning calculations when first opening, but not each time I resize or click on something.
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.
DRay I'd like this improved in Sisense, so it works "out of the box".
Hamza's solutions help, but they're a bit of effort. The workflow will be: a client builds a big model, their UI goes slow, they get frustrated and blame me or Sisense, then either give up or ask me to fix it. Or we add a policy to manually allocate more memory to the model-graphql pod with each deployment, but with the different clients and versions of Sisense I'm involved with, I'd rather not customise more than necessary.
The problem won't happen often, so it doesn't need to be a high priority, but I'd prefer it sorted in a future version sometime.
