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'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.