Hi everyone, We are on 2.7.1 version and the UI is extremely slow, we have imported eks cluster using generic import, the cluster runs 459 nodes. Can you suggest some tuning, we can do to improve UI performance?

The Rancher team are continually, and specifically, making performance improvements. In addition to improvements in 2.7.0 you can find experimental UI improvements in three line burger menu top left --> Global Settings --> Performance. Those are mainly focused at UI list performance. In order to guide is in future improvements it would help us if you could provide as much detail as possible when you say 'the ui is extremely slow', and also roughly the number of resources you imported eks cluster has (specifically 'workloads' types).

@stocky-account-63046 thanks i can see it, can you tell what should i select from settings and configure Should i enable garbage collector and manual refresh?

It depends on what you mean by 'the ui is extremely slow'

The resource loading is taking lot of times, if we move from pages to nodes to pods or to configmaps

Roughly how many pods and configmaps do have in the cluster?

@stocky-account-63046 10k pods

@stocky-account-63046 thank you for the tips is it possible to exclude namespaces from ui? it might help we dont really need all namespaces resources in rancher ui

Fetching all namespaces in a cluster is unavoidable. In terms of fetching all resources regardless of the filter, there's a number of improvements targetted at the next two releases that will help. Some will improve how the dashboard handles lots of resources. some will work by restricting the amount of resources we fetch. More specifically for the latter, one of the changes targetted for 2.7.2 is to only fetch resource from a single namespace, which blocks selection of multiple namespaces or any project/s (this will be updated in following releases to allow more to be selected)

wow, thanks for the update what about excluding specific resources? is it possible? (for example Nodes)

From the video you sent, it looks like even loading the landing page was an issue. It would be good to understand which network requests are consuming the time. Would you be able to provide the output of the browser's dev tools network tab?

yes i will send you in ptivate

at this point, can we stick to screenshots of that network tab?