Optimize the query used to fetch jobs data

RESOLVED INCOMPLETE

Status

Tree Management
Treeherder
P4
normal
RESOLVED INCOMPLETE
3 years ago
9 months ago

People

(Reporter: camd, Unassigned)

Tracking

Details

Attachments

(2 attachments)

(Reporter)

Description

3 years ago
Our query for getting the list of jobs for the resultsets is complex with many joins.  We should optimize this with the proper indexes and such.  Perhaps consulting with a DBA to help get this right.  This query is our main bread-and-butter query that we make all the time for initial page load and job updates.
(Reporter)

Comment 1

3 years ago
Created attachment 8624766 [details]
example query
(Reporter)

Comment 2

3 years ago
Created attachment 8624767 [details]
new relic optimization hints

Updated

3 years ago
Priority: -- → P4
Summary: optimize our jobs query → Optimize the query used to fetch jobs data

Comment 3

9 months ago
The query will have changed considerably, now we're using the ORM.

Let's rely on New Relic for determining which new bugs we need to open for query optimisation.
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.