From owner-freebsd-ports@freebsd.org  Fri Dec 14 04:59:34 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4DF001314EBA;
 Fri, 14 Dec 2018 04:59:34 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D39798AFF7;
 Fri, 14 Dec 2018 04:59:33 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id BD9CB1F611; Fri, 14 Dec 2018 04:59:33 +0000 (UTC)
From: Jan Beich <jbeich@FreeBSD.org>
To: bob prohaska <fbsd@www.zefox.net>
Cc: Christoph Moench-Tegeder <cmt@burggraben.net>,
 freebsd-arm@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: How much memory to compile www/chromium?
References: <20181212165313.GA84881@www.zefox.net>
 <20181212184149.ol44fon2unowu35q@squirrel.exwg.net>
 <20181212192115.GA85583@www.zefox.net>
 <20181212202504.4n3mhtx7grbeh6j7@squirrel.exwg.net>
 <20181214012733.GA92808@www.zefox.net>
Date: Fri, 14 Dec 2018 05:59:21 +0100
In-Reply-To: <20181214012733.GA92808@www.zefox.net> (bob prohaska's message of
 "Thu, 13 Dec 2018 17:27:33 -0800")
Message-ID: <bm5o-wvo6-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-Rspamd-Queue-Id: D39798AFF7
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-0.83 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-0.47)[-0.466,0];
 NEURAL_HAM_SHORT(-0.36)[-0.360,0]
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2018 04:59:34 -0000

bob prohaska <fbsd@www.zefox.net> writes:

> On Wed, Dec 12, 2018 at 09:25:04PM +0100, Christoph Moench-Tegeder wrote:
>
>> ## bob prohaska (fbsd@www.zefox.net):
>> 
>> > > See bsd.ports.mk: DISABLE_MAKE_JOBS (as in "make -DDISABLE_MAKE_JOBS").
>> > >
>> > Thank you, I think that's the information needed. Come to think of it, 
>> > will the -j option, such as -j2, work in this situation also? Two threads
>> > are much better than one 8-)
>> 
>> If you had looked into bsd.port.mk yourself... right below the docs of
>> DISABLE_MAKE_JOBS (line 814) is some documentation for MAKE_JOBS_NUMBER
>> and MAKE_JOBS_NUMBER_LIMIT. -j won't help because there's a lot of
>
> Setting MAKE_JOBS_NUMBER_LIMIT=2 seems to have the desired effect. Still,
> top reports four c++ processes, but only two are running and swap use 
> seldom exceeds 1GB at worst. So far, that's been enough to prevent stalling.
>
> Editing /usr/ports/Mk/bsd.port.mk looks like it'll affect all ports;
> what's the convention for making the change local to www/chromium only?

MAKE_JOBS_NUMBER_LIMIT is a user variable, so you can either set in
make.conf or Makefile.local e.g.,

$ cat <<\. >>${__MAKE_CONF:-/etc/make.conf}
.if ${.CURDIR:M*/www/chromium}
MAKE_JOBS_NUMBER_LIMIT=2
.endif