dashboard icon indicating copy to clipboard operation
dashboard copied to clipboard
verified publisher icon rancher

Backend Performance

Open nwmac opened this issue 4 years ago • 9 comments

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

Tracked as:

  • https://github.com/rancher/rancher/issues/36681
  • https://github.com/rancher/rancher/issues/36682
  • https://github.com/rancher/rancher/issues/36683
  • https://github.com/rancher/rancher/issues/36684
  • https://github.com/rancher/rancher/issues/36685
  • https://github.com/rancher/rancher/issues/38427
  • https://github.com/rancher/rancher/issues/38412
  • https://github.com/rancher/rancher/issues/38428
  • https://github.com/rancher/rancher/issues/38467
  • https://github.com/rancher/rancher/issues/38468

nwmac avatar Mar 01 '22 14:03 nwmac

@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 avatar Mar 04 '22 23:03 cbron

@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 https://github.com/rancher/rancher/issues/36683 - this will allow us to make data retrieval of lists more efficient, if we can exclude large data fields from the response.

nwmac avatar Mar 29 '22 08:03 nwmac

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

samjustus avatar Aug 11 '22 17:08 samjustus

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

We'd also like a start on https://github.com/rancher/rancher/issues/38427 since that will be a big help down the road.

gaktive avatar Aug 11 '22 17:08 gaktive

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

nwmac avatar Aug 17 '22 15:08 nwmac

38427 and #38468 will be our priority for 2.7.1

samjustus avatar Oct 03 '22 13:10 samjustus

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

samjustus avatar Oct 10 '22 18:10 samjustus

Internal reference: SURE-5393

gaktive avatar Oct 12 '22 23:10 gaktive

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

gaktive avatar Oct 13 '22 17:10 gaktive

@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 avatar Oct 26 '22 09:10 nwmac

Added and/or ported over from Jira:

  • https://github.com/rancher/rancher/issues/40140
  • https://github.com/rancher/rancher/issues/40141
  • https://github.com/rancher/rancher/issues/40771
  • https://github.com/rancher/rancher/issues/40772
  • https://github.com/rancher/rancher/issues/40773

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.

gaktive avatar Mar 03 '23 23:03 gaktive

Added https://github.com/rancher/rancher/issues/39568 above upon request.

gaktive avatar Mar 14 '23 23:03 gaktive

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

richard-cox avatar May 24 '23 11:05 richard-cox

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

gaktive avatar Jul 27 '23 15:07 gaktive