Closed
Bug 1509999
Opened 6 years ago
Closed 6 years ago
Increase minimum capacity for decision task worker types
Categories
(Taskcluster :: Operations and Service Requests, task)
Taskcluster
Operations and Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Assigned: bstack)
References
Details
Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1500400#c5, we should bump the minimum # of decision task workers from 1 to 5 to ensure throughput under peak load.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bstack
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•6 years ago
|
||
I have bumped min capacity for gecko{1,2,3}-decision workertypes to 5 across the board from 1, 0, and 1 respectively.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Comment 2•6 years ago
|
||
Looking through the level-2 repos in https://hg.mozilla.org/build/ci-configuration/file/tip/projects.yml, only one of them (https://hg.mozilla.org/projects/larch) has commits this half, so we could perhaps have a lower minimum for gecko2-decision. Might not be worth it though.
Assignee | ||
Comment 3•6 years ago
|
||
Ok, makes sense. I'll turn level-2 down to 1.
Updated•5 years ago
|
Component: Operations → Operations and Service Requests
You need to log in
before you can comment on or make changes to this bug.
Description
•