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

Backend Performance #5243

Open
nwmac opened this issue Mar 1, 2022 · 14 comments
Open

Backend Performance #5243

nwmac opened this issue Mar 1, 2022 · 14 comments

Comments

@nwmac
Copy link
Member

nwmac commented Mar 1, 2022

Revisit UI once some performance improvements on the backend are made.

Tracked as:

Requested By BE

@nwmac nwmac added this to the v2.6.5 milestone Mar 1, 2022
@nwmac nwmac self-assigned this Mar 1, 2022
@cbron
Copy link
Contributor

cbron commented Mar 4, 2022

@nwmac to what extent are these required in 2.6.5 ? Is UI planning to do some work around them, and what are those deadlines.

@nwmac
Copy link
Member Author

nwmac commented Mar 29, 2022

@cbron We aren't planning on doing any work around them now in 2.6.5 - given the short timeframe we can push them out to next release - but we will need them done early to give us to time to use them in the UI.

The most important one for us is rancher/rancher#36683 - this will allow us to make data retrieval of lists more efficient, if we can exclude large data fields from the response.

@samjustus
Copy link

samjustus commented Aug 11, 2022

36681 & 38412 are going to be our top priority for 2.7, unless advised otherwise.

@gaktive
Copy link
Member

gaktive commented Aug 11, 2022

@samjustus Upon discussion with UI based on current needs, along with rancher/rancher#36681 and rancher/rancher#38412 (the latter of which @aalves08 is collecting more data on simultaneous users), we'd ask for rancher/rancher#36682 and rancher/rancher#38467 to be prioritized too.

We'd also like a start on rancher/rancher#38427 since that will be a big help down the road.

@gaktive gaktive added the team/area1 Team Neo label Aug 11, 2022
@nwmac
Copy link
Member Author

nwmac commented Aug 17, 2022

@cbron @samjustus Anything you can do on rancher/rancher#38468 for 2.7? Norman is 3 times quicker than Steve at returning data.

@samjustus
Copy link

samjustus commented Oct 3, 2022

38427 and #38468 will be our priority for 2.7.1

@samjustus
Copy link

@nwmac @gaktive Can you please create Jira issues for all of these? Per the new process Denise outlined in Management meeting today (10/10)

@gaktive gaktive modified the milestones: v2.7.x, v2.7.1 Oct 12, 2022
@gaktive gaktive added the JIRA label Oct 12, 2022
@gaktive
Copy link
Member

gaktive commented Oct 12, 2022

Internal reference: SURE-5393

@gaktive
Copy link
Member

gaktive commented Oct 13, 2022

Priority tickets based on current thinking and consensus:
1 with all the stars: rancher/rancher#38427
2. rancher/rancher#38412
3. rancher/rancher#38468

@nwmac
Copy link
Member Author

nwmac commented Oct 26, 2022

@gaktive Bumping this to 2.7.2 - this issue is for tracking - there is nothing for us to do in 2.7.1 that is not tracked in other issues.

@nwmac nwmac removed this from the v2.7.1 milestone Oct 26, 2022
@gaktive
Copy link
Member

gaktive commented Mar 14, 2023

Added rancher/rancher#39568 above upon request.

@richard-cox
Copy link
Member

A number of the referenced issues have been closed and not completed, some without comment. Needs investigating

@gaktive gaktive modified the milestones: v2.7.next3, v2.7.next4 May 24, 2023
@gaktive
Copy link
Member

gaktive commented Jul 27, 2023

I'll work on tidying this up with @nwmac when he's back.

@nwmac nwmac modified the milestones: v2.8.0, v2.8.next1 Aug 16, 2023
@nwmac nwmac assigned richard-cox and unassigned nwmac Mar 5, 2024
@nwmac nwmac added the QA/None label Mar 7, 2024
@nwmac nwmac modified the milestones: v2.9.0, v2.10.0 Mar 21, 2024
@nwmac nwmac modified the milestones: v2.10.0, v2.11.0 Jul 4, 2024
@richard-cox richard-cox modified the milestones: v2.10.0, v2.11.0 Sep 19, 2024
@nwmac nwmac modified the milestones: v2.12.0, v2.11.0 Nov 1, 2024
@richard-cox richard-cox modified the milestones: v2.11.0, v2.12.0 Nov 7, 2024
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

6 participants