Backend: Improve performance of PATCH /api/:version/jobs/:id/trace

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The following discussion from !80965 (merged) should be addressed:

• @reprazent started a discussion:

  Should we already create an issue for this one that will not meet it's target?

In the process of assigning custom Apdex targets for CI job-related endpoints, we assigned PATCH trace with a default urgency, it is not currently meeting this SLI, so we should improve the performance:

json.meta.caller_id.keyword	99.5th percentile of json.duration_s	99.8th percentile of json.duration_s	Count	Met urgency	Target urgency
PATCH /api/:version/jobs/:id/trace	1.25121	2.89419	105,986,684	low	default

Investigation table

Description	Link	Milestone	Timeframe
Assign custom Apdex targets for CI jobs endpoints	#344667 (closed)	%14.9	~"FY22::Q4"
Set low urgency as Apdex targets for remaining PE endpoints	#360273 (closed)	%15.0	~"FY23::Q2"
Remove ignored_components from PE error budget	#348552 (closed)	%15.0	~"FY23::Q2"
Introduce Keyset pagination for GET /api/:version/projects/:id/jobs API endpoint	#362172 (closed)	%15.5	~"FY23::Q3"
Backend: Improve performance of GraphqlController#execute	#361377	TBD	~"FY23::Q3"
Backend: Improve performance of PATCH /api/:version/jobs/:id/trace	👈 You are here	TBD	~"FY23::Q3"
Assign custom Apdex targets for remaining PE endpoints	#348554	TBD	~"FY23::Q3"