Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-04-02 Thread Kevin Kofler via devel
Nico Kadel-Garcia wrote: > It happens locally, rather than formally in koji or mock. I've had to > use it to build things like "cli53", which has a stunning mess of > golang dependencies hosted in github and beyond my ability to sort out > the dependency chains. I've also used it for pip based

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-04-01 Thread Nico Kadel-Garcia
On Thu, Apr 1, 2021 at 8:37 AM Kevin Kofler via devel wrote: > > Nico Kadel-Garcia wrote: > > Let's *not*. The amount of space saved in storage by putting socks and > > underwear in their own separate drawers os often overwhelmed by the > > space wasted in giving those drawers sides and a way to

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-04-01 Thread Kevin Kofler via devel
Nico Kadel-Garcia wrote: > Let's *not*. The amount of space saved in storage by putting socks and > underwear in their own separate drawers os often overwhelmed by the > space wasted in giving those drawers sides and a way to slide in and > out. In other words, it creates unnecessary overhead in

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-30 Thread Panu Matilainen
On 3/30/21 12:43 PM, Nico Kadel-Garcia wrote: On Tue, Mar 30, 2021 at 4:46 AM Panu Matilainen wrote: On 3/29/21 8:17 PM, Michel Alexandre Salim wrote: Hi again, On Fri, 2021-03-26 at 17:29 -0700, Michel Alexandre Salim wrote: [snip] Right now I'm just overriding _smp_build_ncpus to 1,

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-30 Thread Nico Kadel-Garcia
On Tue, Mar 30, 2021 at 4:46 AM Panu Matilainen wrote: > > On 3/29/21 8:17 PM, Michel Alexandre Salim wrote: > > Hi again, > > > > On Fri, 2021-03-26 at 17:29 -0700, Michel Alexandre Salim wrote: > >> > > [snip] > >> Right now I'm just overriding _smp_build_ncpus to 1, but there is a > >> more

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-30 Thread Panu Matilainen
On 3/29/21 8:17 PM, Michel Alexandre Salim wrote: Hi again, On Fri, 2021-03-26 at 17:29 -0700, Michel Alexandre Salim wrote: [snip] Right now I'm just overriding _smp_build_ncpus to 1, but there is a more elegant solution I'd like to propose: What if one can declaratively set the required

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-29 Thread Michel Alexandre Salim
Hi again, On Fri, 2021-03-26 at 17:29 -0700, Michel Alexandre Salim wrote: > [snip] > Right now I'm just overriding _smp_build_ncpus to 1, but there is a > more elegant solution I'd like to propose: > > What if one can declaratively set the required RAM per build job -- > either with a single

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-29 Thread Miroslav Suchý
Dne 27. 03. 21 v 1:29 Michel Alexandre Salim napsal(a): Is there interest in having this be available? I could imagine it might be useful for other resource-intensive package builds e.g. for Chromium. Definitely. Additionally see https://pagure.io/copr/copr/issue/1678 for declaring timeout.

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-28 Thread Dan Čermák
Hi Michel, Michel Alexandre Salim writes: > Hi all, > > This idea came about when I'm debugging build issues with mcrouter, > which turns out to be due to build jobs failing to allocate memory and > getting terminated without aborting the entire compilation, causing > link issues when empty or

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-27 Thread Dan Horák
On Fri, 26 Mar 2021 17:29:27 -0700 Michel Alexandre Salim wrote: > Hi all, > > This idea came about when I'm debugging build issues with mcrouter, > which turns out to be due to build jobs failing to allocate memory and > getting terminated without aborting the entire compilation, causing >

Re: RFC: declaring estimated per-builder RAM usage in spec file

2021-03-26 Thread Dennis Gilmore
perhaps you should look at how ceph has dealt with a similar issue, they set the max number of cpus based on the system ram. https://src.fedoraproject.org/rpms/ceph/blob/rawhide/f/ceph.spec#_1246 Dennis On Fri, Mar 26, 2021 at 7:49 PM Michel Alexandre Salim wrote: > > Hi all, > > This idea came

RFC: declaring estimated per-builder RAM usage in spec file

2021-03-26 Thread Michel Alexandre Salim
Hi all, This idea came about when I'm debugging build issues with mcrouter, which turns out to be due to build jobs failing to allocate memory and getting terminated without aborting the entire compilation, causing link issues when empty or corrupted objects are encountered: