On Freitag, 27. Oktober 2017, 07:49:10 CEST wrote Jimmy Berry:
Does OBS prioritize large/important jobs to more
Leap:15.0 has 40% of packages blocked at this point by one very slow job. The
page shows it not even half done and over the 100% mark based on previous.
Contrast that with the OBS monitor page shows ~75% of workers idle.
It would seem straight-forward and very beneficial to prioritize packages that
block lots of others and secondary to that longer build times onto more
powerful machines. I have done this sort of optimization for job queues
elsewhere and seen major improvements.
I have also seen the same sort of behavior with libreoffice builds which are
far too long under the best of circumstances and awful when they are slower.
Does OBS have any prioritization besides based on the project in which the
yes, but not in this regard. The dispatcher takes the trigger reason
into account in first place (new builds or source changed builds a prefered).
A prefer of "more important jobs" it not so easy, given that there is not a
value to rate a worker. Some jobs are disk IO bound, some are memory bound, others
are cpu bound and yet another ones need special cpu hardware features to be faster.
Also the build graph can change on every build, so it is not taken into account.
However, you can of course define constraints to require a certain number cpus, memory
or alike for packages which you see critical.
It seems one can even recognize the stalemate on the
overview graph  which
shows the blocked flattening out much more quickly (even before making it to
the previous flat).
That graph shows in first place that there the speed of the dispatcher was a bottle
neck in first place. Not all workers were used, but jobs did exist. This can happen
when some workers slowing down the answer on job assignment.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org