Closed
Bug 1239419
Opened 9 years ago
Closed 8 years ago
Coalescer needs a threshold setting
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dividehex, Assigned: dividehex)
References
Details
The coalescer app needs a threshold setting so we don't coalesce on all task queues greater than one. This should be probably be dynamically set via the api as opposed to a ENV setting. All logic should be contained to the coalescer service and not within the worker. One idea is to return an list with only the calling taskid if queue size is below current threshold and return the entire actual taskid list if equal to or above the threshold
Comment 1•9 years ago
|
||
I tend to think that the threshold should be a combination: queue length > N && oldest task age > M. Then even if we dump 100 tasks in with the same key within a short time, if we have the capacity to start them all immediately, we can avoid coalescing.
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 2•8 years ago
|
||
Pending the review and merge of https://github.com/mozilla/tc-coalesce/pull/12, this will be complete.
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•