Closed Bug 1221064 Opened 9 years ago Closed 9 years ago

The job list endpoint times out when the result_set_id filter is not used

Categories

(Tree Management :: Treeherder: API, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mdoglio, Assigned: mdoglio)

References

Details

Attachments

(2 files)

47 bytes, text/x-github-pull-request
emorley
: review+
Details | Review
49 bytes, text/x-github-pull-request
emorley
: review+
Details | Review
I believe the join with the resultset table is taking too much space in memory. We should probably make that join only when that filter is set.
Attached file PR 1111
Assignee: nobody → mdoglio
Status: NEW → ASSIGNED
Attachment #8682487 - Flags: review?(emorley)
Comment on attachment 8682487 [details] [review] PR 1111 Cancelling whilst the PR is updated :-)
Attachment #8682487 - Flags: review?(emorley)
Attachment #8682487 - Flags: review?(emorley)
Attachment #8682487 - Flags: review?(emorley) → review+
Commits pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/caa8cb0f820084e2d7fb57448bb9cee121a3c664 Bug 1221064 - add new similar jobs endpoint This endpoint will be used by the similar jobs panel in the ui. It returns a list of jobs shaped in the same way as the job list endpoint but ordered by resultset_id DESC. In order to achieve decent performance the returned list is filtered by the same job type as the one selected. https://github.com/mozilla/treeherder/commit/6cdbfa89b154b7767eda92d195f0d4a35d5022b0 Bug 1221064 - change source endpoint for the similar jobs panel Let's use the new endpoint to keep the sorting in the similar jobs list right. https://github.com/mozilla/treeherder/commit/9701ea433b4f4ca5901cf0716c2d33ac596dbe70 Bug 1221064 - improve job list performance The job list endpoint was joining the job table and the resultset table with the only purpose of sorting the results by push_timestamp.Also we don't really need any sorting on that endpoint, so let's remove it.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Depends on: 1221707
Hmm I wonder if this is going to affect other consumers of the /jobs/ API?
Blocks: 1211415
Attached file PR 1124
Attachment #8683676 - Flags: review?(emorley)
Attachment #8683676 - Flags: review?(emorley) → review+
(In reply to Treeherder Bugbot from comment #6) > Commit pushed to master at https://github.com/mozilla/treeherder > > https://github.com/mozilla/treeherder/commit/ > 761ae7f163d0550b124045125255cd0c3b7bd415 > Bug 1221064 - make the job list order explicit I ended up reverting this since it seems to be a contributing factor to DB load at the moment. The first and last deploy markers here are when it landed and was reverted: https://rpm.newrelic.com/accounts/677903/applications/4180461/datastores?tw%5Bend%5D=1447189515&tw%5Bstart%5D=1447167915#/overview/All/drilldown?metric=Datastore%252Fstatement%252FMySQL%252Fjob%252Fselect&value=total_call_time_per_minute
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/0ecb647f795c15604b191c5b4010956068b9fb8f Revert "Bug 1221064 - make the job list order explicit" This reverts commit 761ae7f163d0550b124045125255cd0c3b7bd415.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: