On Wed, Jul 01, 2020 at 02:00:09PM +0200, Jan Kratochvil wrote: > On Wed, 01 Jul 2020 13:43:57 +0200, Stephen John Smoogen wrote: > > In the end we have limited resources and you are running into those > > limits. We can either have fewer builders with more disk space and a > > long queue of builds or we can have more builders with smaller disk > > space. > > Good to know disk space really is a limiting factor there (as it is in general > cheap compared to CPUs+RAM). > > Sure a best step would be to have multiple (two) kinds of builders > with different disk sizes and blacklist/whitelist packages to > them. I am aware that idea is obvious, is there a Koji patch needed > or even administration of two kinds of builders is too much? I know from the RISC-V Koji instance that given enough permissions it is possible to direct jobs to particular build hosts. We do it manually for jobs we know will be very large/long (hello there gcc!) Maybe a way to direct jobs based on regexp of their name would be a useful feature to propose/implement upstream? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
