Faster UI for large datamodels

[Tim]

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.

[dougnewton]

Maybe a setting at the model level for "auto-rearrange", which is checked by default.  (The current behavior)   It would let you un-check it to turn off that feature and maintain the arrangement manually.

[Tim]

I see Windows Sisense had an "ElastiCube Manager". Does that handle lots of tables? Maybe something similar for Web, or as a downloadable program that can link to the Sisense server.

[HamzaJ]

We ran into this issue aswell. With the help of support we fixed this by replicating the model-graphql pod (from 1 to 2) and increasing its memory.

[Tim]

@HamzaJ How do you do that? I might try that.

[HamzaJ]

Hello @Tim ,

1. Login to Sisense server

2. Run the command

   kubectl -n sisense get deployments.apps model-graphql -o yaml | grep -A2 replicas

   In case you see 1 replica you need to adjust it to 2. If you already have more than 1, add 1 to that number

3. Run the command

   kubectl -n sisense edit deployment model-graphql

4. Find "spec: replicas" (see the screenshot) and update replicas number (press “i” on the keyboard to enter edit mode → edit value → ESC to exit edit mode → use “:wq!” to exit and save changes)

Solution 2: Increase memory limit in model-graphql deployment

Be sure that you know what you are doing (also make a backup). Otherwise reach out to sisense support to assist you.

[DRay]

Hi @Tim.

Did the steps provided by @HamzaJ resolve the issue for you?

[Tim]

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.

[HamzaJ]

Hey @Tim ,

Here is a Sisense post with instructions to change the memory limit of a pod:

https://community.sisense.com/t5/knowledge/build-stability-improvements-on-heavy-loaded-systems/ta-p...

Hamza