Identify and address performance challenges in the Code Quality Report API endpoint

Why are we doing this work

Error budgets have been created to help us understand the reliability and availability of our features. The error budget we have can be quickly exhausted by endpoints which have a high percentage of slow requests. A slow request is currently defined as taking more than 1s to respond.

Over 53% of the requests each week against the Code Quality report API take longer than 1s to respond. This is, by far, the least responsive endpoint currently owned by groupstatic analysis as judged by a percentage of traffic it services. Making this endpoint more responsive and able to consistently respond in less than 1 second would go along way towards making Static Analysis compliant with our stated error budget.

Relevant links

• Static Analysis error budget dashboard
• APDEX violations in past week
• Error budget documentation in the handbook
• Documentation for reading error budget dashboards

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan