Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve rancher performance by updating Extensions to be inline with server-side pagination #13185

Open
7 tasks
Tracked by #8527
richard-cox opened this issue Jan 23, 2025 · 0 comments
Open
7 tasks
Tracked by #8527

Comments

@richard-cox
Copy link
Member

richard-cox commented Jan 23, 2025

Many extensions will fetch all of a resource type anyway, negating and making the performance worse in SSP world. For example if a user flicks between the cluster configmap list (fetch a page) and a kw page where all config maps are fetched, each indivual visit will clear the cache and make a new request (can be costly when fetching all)

Extensions can also gain the benefit of SSP performance bump

Issues to be created in extension specific repos

  • Improve Fleet performance (server-side pagination, remove findAlls)
  • [ENHANCEMENT] Improve Harvester UI Extension Performance (placeholder) harvester/harvester#7342
  • Improve KubeWarden performance (server-side pagination, remove findAlls)
  • Improve Elemental performance (server-side pagination, remove findAlls)
  • Improve NeuVector performance (server-side pagination, remove findAlls)
  • Improve StackState performance (server-side pagination, remove findAlls)
  • Other Rancher Extensions?
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 23, 2025
@richard-cox richard-cox added kind/enhancement QA/None area/server-side-pagination area/performance and removed QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Jan 23, 2025
@richard-cox richard-cox added this to the v2.11.1 milestone Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant