Re: Copr routinely swamped by nightly builds
On 02/17/2015 01:36 PM, Kevin Fenzi wrote: Wouldn't it be better to (c) implement some sort of 'fair' scheduling instead of a pure first-come-first-serve system? Yes, that also has been talked about. I don't know where it is in implementation however. I've started a feature branch to tackle this problem. At first we would limit number of builders allocated to the one user (important for heavy packages like kernel or chromium), and also re-use VM for the same user (big deal for coprs with bunch of small srpm). Rought ETA ~1 month. If copr is still spawmped in future, we will introduce some dynamic prioritization. -- Best regards, Gologuzov Valentin. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Copr routinely swamped by nightly builds
2015-02-17 5:34 GMT+01:00 Kevin Kofler kevin.kof...@chello.at: IMHO, one of 2 things needs to happen: a) Copr gets a massive increase of resources (builders) to handle the load, OR b) we disallow nightly builds of huge packages such as python3 in Copr, because the infrastructure does not scale to that kind of load. Kevin Kofler Wouldn't it be better to (c) implement some sort of 'fair' scheduling instead of a pure first-come-first-serve system? Because (a) sounds unlikely, and (b) seems hard to define properly (what is a 'huge' package? when is 'night'? and when are people allowed to do these builds?) and also hard to enforce. - Thomas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Copr routinely swamped by nightly builds
On Tue, 17 Feb 2015 11:35:57 +0100 Thomas Moschny thomas.mosc...@gmail.com wrote: 2015-02-17 5:34 GMT+01:00 Kevin Kofler kevin.kof...@chello.at: IMHO, one of 2 things needs to happen: a) Copr gets a massive increase of resources (builders) to handle the load, OR b) we disallow nightly builds of huge packages such as python3 in Copr, because the infrastructure does not scale to that kind of load. Kevin Kofler a) is in progress. We have hardware, just working on setting up a much more recent openstack. Once thats in and stable and maintainable, we should be able to increase the number of builders a great deal. Wouldn't it be better to (c) implement some sort of 'fair' scheduling instead of a pure first-come-first-serve system? Yes, that also has been talked about. I don't know where it is in implementation however. kevin pgpIWtR0tpdIW.pgp Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Copr routinely swamped by nightly builds
Hi, I have repeatedly run into insane delays (hours) for my builds to happen (read: to even start, i.e., to get out of the pending phase), because lately, some automated nightly builds have been monopolizing the builders every night. The worst are the Python 3 nightly builds from churchyard/python3-nightly that sometimes take hours to build (and in the best case, still around 50 minutes)! IMHO, one of 2 things needs to happen: a) Copr gets a massive increase of resources (builders) to handle the load, OR b) we disallow nightly builds of huge packages such as python3 in Copr, because the infrastructure does not scale to that kind of load. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
