Discuss/investigate dynamic application of server-side pagination

[richard-cox]

• At the moment SSP is enabled by Feature Flag and then Performance Setting (which includes specific resources / contexts)
  • When not enabled the UI continues as before and fetches all of that resource type
    • This results in few calls but they can be massive in duration and payload
  • When enabled resource lists will only fetch sub-sets of the required resource type
    • This results in a lot more requests but with potentially massively smaller payloads
      • requests made every time a list is shown, resource change, sort/filter change. 3x requests for cluster side nav list on cluster state change, etc
• To discuss
  • should we add more dynamic handling of SSP enabled state via resource count
  • this would mean
    • UI looking at clusters with tiny amount of resources remain super responsive (initial request to get all resources is small, avoids additional http requests for type)
    • UI looking at clusters with a large amount of resources remain responsive (many small requests)