Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Am Mi., 5. Jan. 2022 um 21:21 Uhr schrieb Sam James : > >> On 5 Jan 2022, at 19:18, Kai Krakow wrote: > >>> Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller : > > [...] > >>> That applies to all parallel builds though, not only to ebuilds >>> inheriting check-reqs.eclass. By tweaking MAKEO

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.05 21:10, David Seifert wrote: > On Wed, 2022-01-05 at 21:06 +, Roy Bamford wrote: > > On 2022.01.05 20:22, Sam James wrote: > > > > > > > > > > On 5 Jan 2022, at 19:02, Roy Bamford > > > wrote: > > > > > > > > Sam, > > > > > > > > Do users with FEATURES=distcc still have to opt

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Roy Bamford wrote: > On 2022.01.05 20:22, Sam James wrote: >> >>> On 5 Jan 2022, at 19:02, Roy Bamford >> wrote: >>> Sam, >>> >>> Do users with FEATURES=distcc still have to opt out of this >>> MAKEOPTS clamping? >>> >> Great point! I think we could add an exemption for that and make it a >> noop

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Sam James wrote: >> On 5 Jan 2022, at 08:28, Ulrich Mueller wrote: >> >> Where does this number 2 GB come from? The amount of RAM strongly >> depends on the programming language and other factors, so I don't >> believe that there's one number that can be used for every

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Wed, 2022-01-05 at 21:06 +, Roy Bamford wrote: > On 2022.01.05 20:22, Sam James wrote: > > > > > > > On 5 Jan 2022, at 19:02, Roy Bamford > > wrote: > > > > > > Sam, > > > > > > Do users with FEATURES=distcc still have to opt out of this > > > MAKEOPTS clamping? > > > > > > > Great po

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.05 20:22, Sam James wrote: > > > > On 5 Jan 2022, at 19:02, Roy Bamford > wrote: > > > > Sam, > > > > Do users with FEATURES=distcc still have to opt out of this > > MAKEOPTS clamping? > > > > Great point! I think we could add an exemption for that and make it a > noop or warning-

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Wed, 2022-01-05 at 09:28 +0100, Ulrich Mueller wrote: > > > > > > On Tue, 04 Jan 2022, Sam James wrote: > > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > > amount of RAM available (uses amount declared as needed > > in the ebuild). Typically should be ~2GB per job. > > Whe

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 17:51, Alec Warner wrote: > On Tue, Jan 4, 2022 at 3:03 PM Sam James wrote: >> >> On 4 Jan 2022, at 22:58, Sam James wrote: >> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >> amount of RAM available (uses amount declared as needed >> in the ebuild). Typic

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:02, Roy Bamford wrote: > > Sam, > > Do users with FEATURES=distcc still have to opt out of this > MAKEOPTS clamping? > Great point! I think we could add an exemption for that and make it a noop or warning-only. Best, sam signature.asc Description: Message signed w

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:18, Kai Krakow wrote: > > Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller >: >> >>> [...] >> That applies to all parallel builds though, not only to ebuilds >> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >> te

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 08:28, Ulrich Mueller wrote: > >> On Tue, 04 Jan 2022, Sam James wrote: > >> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >> amount of RAM available (uses amount declared as needed >> in the ebuild). Typically should be ~2GB per job. > > Where does th

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 5 Jan 2022, at 19:53, Ulrich Mueller wrote: > >> On Wed, 05 Jan 2022, Florian Schmaus wrote: > >>> That applies to all parallel builds though, not only to ebuilds >>> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >>> telling the user that the --jobs setting in th

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Florian Schmaus wrote: >> That applies to all parallel builds though, not only to ebuilds >> inheriting check-reqs.eclass. By tweaking MAKEOPTS, we're basically >> telling the user that the --jobs setting in their make.conf is wrong, >> in the first place. > Yes, exactl

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Am Mi., 5. Jan. 2022 um 19:22 Uhr schrieb Ulrich Mueller : > > > On Wed, 05 Jan 2022, Florian Schmaus wrote: > > > On 05/01/2022 09.28, Ulrich Mueller wrote: > >>> On Tue, 04 Jan 2022, Sam James wrote: > >>> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > >>> amount of RAM

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 05/01/2022 19.22, Ulrich Mueller wrote: On Wed, 05 Jan 2022, Florian Schmaus wrote: On 05/01/2022 09.28, Ulrich Mueller wrote: On Tue, 04 Jan 2022, Sam James wrote: Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the amount of RAM available (uses amount declared as needed in th

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 2022.01.04 22:58, Sam James wrote: > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug: https://bugs.gentoo.org/570534 > Signed-off-by: Sam James > --- > eclass/c

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Wed, 05 Jan 2022, Florian Schmaus wrote: > On 05/01/2022 09.28, Ulrich Mueller wrote: >>> On Tue, 04 Jan 2022, Sam James wrote: >>> Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the >>> amount of RAM available (uses amount declared as needed >>> in the ebuild). Typically

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On Tue, Jan 4, 2022 at 3:03 PM Sam James wrote: > > > > On 4 Jan 2022, at 22:58, Sam James wrote: > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug: https://bugs.

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

I do sometimes run into OOM during emerge, but for a different reason: when firefox and webengine are built in parallel. And I'm using tmpfs for portage. These packages store lots of data in the build directory. Decreasing -j of a single package may or may not help in this case. The filled tmp

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

On 05/01/2022 09.28, Ulrich Mueller wrote: On Tue, 04 Jan 2022, Sam James wrote: Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the amount of RAM available (uses amount declared as needed in the ebuild). Typically should be ~2GB per job. Where does this number 2 GB come from? The a

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On Tue, 04 Jan 2022, Sam James wrote: > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. Where does this number 2 GB come from? The amount of RAM strongly depends on t

Re: [gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

> On 4 Jan 2022, at 22:58, Sam James wrote: > > Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the > amount of RAM available (uses amount declared as needed > in the ebuild). Typically should be ~2GB per job. > > Bug: https://bugs.gentoo.org/570534 > Signed-off-by: Sam James > ---

[gentoo-dev] [PATCH] check-reqs.eclass: clamp MAKEOPTS for memory/RAM usage

Crank down MAKEOPTS jobs if MAKEOPTS="-jN" is too high for the amount of RAM available (uses amount declared as needed in the ebuild). Typically should be ~2GB per job. Bug: https://bugs.gentoo.org/570534 Signed-off-by: Sam James --- eclass/check-reqs.eclass | 42