This spike is meant to answer the question "Using the existing implementation and API, which screens in the new ui will cause performance issues at quay.io scale?"

Acceptance Criteria:

• A doc exists that includes the following:
  • All screens in the new UI have been examined and API calls identified
  • Estimations on what happens at scale have been made
  • Recommendations for mitigating potential performance issues