-
Notifications
You must be signed in to change notification settings - Fork 266
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
Comments
@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. |
@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 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. |
@cbron @samjustus Anything you can do on rancher/rancher#38468 for 2.7? Norman is 3 times quicker than Steve at returning data. |
Internal reference: SURE-5393 |
Priority tickets based on current thinking and consensus: |
@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. |
Added and/or ported over from Jira:
Down the road, this epic should focus on what's deliverable for Q2 with a new epic spawned to then copy work to then tackle in Q3. |
Added rancher/rancher#39568 above upon request. |
A number of the referenced issues have been closed and not completed, some without comment. Needs investigating |
I'll work on tidying this up with @nwmac when he's back. |
Revisit UI once some performance improvements on the backend are made.
Tracked as:
Requested By BE
The text was updated successfully, but these errors were encountered: