Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 25 Jan 2020 15:59:06 -0800
From:      Cy Schubert <Cy.Schubert@cschubert.com>
To:        sgk@troutmask.apl.washington.edu
Cc:        Cy Schubert <Cy.Schubert@cschubert.com>, freebsd-current@freebsd.org, Mark Millard <marklmi@yahoo.com>, yasu@utahime.org
Subject:   Re: After update to r357104 build of poudriere jail fails with  'out of swap space'
Message-ID:  <202001252359.00PNx6n1007151@slippy.cwsent.com>
In-Reply-To: <20200125233116.GA49916@troutmask.apl.washington.edu>
References:  <DAA3A910-25F2-447A-B540-C35985DA822E.ref@yahoo.com>  <DAA3A910-25F2-447A-B540-C35985DA822E@yahoo.com> <A6C8D5FD-EC99-4846-8F43-ABE7B6D27D03@cschubert.com> <20200125215203.GA49253@troutmask.apl.washington.edu> <3B744DB0-35ED-44FE-8235-A16EE5F925CA@cschubert.com> <20200125233116.GA49916@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20200125233116.GA49916@troutmask.apl.washington.edu>, Steve 
Kargl w
rites:
> On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote:
> > On January 25, 2020 1:52:03 PM PST, Steve Kargl <sgk@troutmask.apl.washingt
> on.edu> wrote:
> > >On Sat, Jan 25, 2020 at 01:41:16PM -0800, Cy Schubert wrote:
> > >> 
> > >> It's not just poudeiere. Standard port builds of chromium, rust
> > >> and thunderbird also fail on my machines with less than 8 GB.
> > >>
> > >
> > >Interesting.  I routinely build chromium, rust, firefox,
> > >llvm and few other resource-hunger ports on a i386-freebsd
> > >laptop with 3.4 GB available memory.  This is done with
> > >chrome running with a few tabs swallowing a 1-1.5 GB of
> > >memory.  No issues.  
> > 
> > Number of threads makes a difference too. How many core/threads does your l
> aptop have?
>
> 2 cores.

This is why.

>
> > Reducing number of concurrent threads allowed my builds to complete
> > on the 5 GB machine. My build machines have 4 cores, 1 thread per
> > core. Reducing concurrent threads circumvented the issue. 
>
> I use portmaster, and AFIACT, it uses 'make -j 2' for the build.
> Laptop isn't doing too much, but an update and browsing.  It does
> take a long time especially if building llvm is required.

I use portmaster as well (for quick incidental builds). It uses 
MAKE_JOBS_NUMBER=4 (which is equivalent to make -j 4). I suppose machines 
with not enough memory to support their cores with certain builds might 
have a better chance of having this problem.

MAKE_JOBS_NUMBER_LIMIT to limit a 4 core machine with less than 2 GB per 
core might be an option. Looking at it this way, instead of an extra 3 GB, 
the extra 60% more memory in the other machine makes a big difference. A 
rule of thumb would probably be, have ~ 2 GB RAM for every core or thread 
when doing large parallel builds.


-- 
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202001252359.00PNx6n1007151>