tasks queued for the launchpad build farm can be starved out by bulk work, and bulk work can be starved by interactive work
Bug #810720 reported by
Francis J. Lacoste
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
The current score-based queued algorithm is pretty primitive. We want to be able to better segment the build resources across our users. We would like also to be able to provide strict SLA to certain class of users, while at the same time ensuring that no builds is ever starved.
Some (but not exhaustive use cases):
* We want time-sensitive Ubuntu rebuilds to progress rapidly while not hogging the build farm from other users.
* We want to provide strict SLA for commercial sensitive builds (Landscape, OEM, etc.)
* etc.
This needs to be turned into a proper LEP, but is a reminder to do so.
To post a comment you must log in.
In the ideal world this would turn into something that has dynamic weightings controlled from a page in LP that has a lot of knobs and dials. For example, we might want to weight rebuilds more heavily, turn down a PPA that has a lot of builds swamping the farm, or temporarily promote language packs. There are a lot of variables.