From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#27476: guix pull fails on powerful server
Date: Tue, 10 Oct 2017 13:32:30 +0200
Message-ID: <87wp43nsq9.fsf__18835.6069884778$1507635200$gmane$org@gnu.org>
References: <87h8vvp1q7.fsf@elephly.net> <87377esu1a.fsf@gnu.org>
	<87k20nz18u.fsf@igalia.com> <87a81jj5gg.fsf@gnu.org>
	<87bmlyzxj7.fsf@elephly.net> <87shf44ny0.fsf@elephly.net>
	<87po9zj8lt.fsf@gnu.org> <878tgjmpz6.fsf@elephly.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51299)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1e1smV-0002By-4L
	for bug-guix@gnu.org; Tue, 10 Oct 2017 07:33:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1e1smU-0006zQ-8M
	for bug-guix@gnu.org; Tue, 10 Oct 2017 07:33:03 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:50645)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1e1smU-0006yw-4G
	for bug-guix@gnu.org; Tue, 10 Oct 2017 07:33:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1e1smT-0007A8-Uj
	for bug-guix@gnu.org; Tue, 10 Oct 2017 07:33:01 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.27476.B27476.150763516527491@debbugs.gnu.org>
In-Reply-To: <878tgjmpz6.fsf@elephly.net> (Ricardo Wurmus's message of "Tue,
	10 Oct 2017 09:17:17 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Andy Wingo <wingo@igalia.com>, help-guix@gnu.org, 27476@debbugs.gnu.org

Ricardo Wurmus <rekado@elephly.net> skribis:

> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>
>>> I=E2=80=99ve tried =E2=80=9Cguix pull=E2=80=9D on the same server again=
, this time limiting CPUs
>>> with =E2=80=9Ctaskset -c 0 guix pull=E2=80=9D:
>>
>> As a stopgap, commit aba219af0fed6a349af930f19c913fb87e6a69dd ensures
>> that =E2=80=98--cores=E2=80=99 is honored.  So if you run =E2=80=9Cguix =
pull --cores=3D1=E2=80=9D, it will
>> build things sequentially.
>>
>> Now, to take advantage of that, you first need to update to the current
>> Guix=E2=80=A6
>
> Thank you, this worked!
>
> On that server I built Guix from source and then let the users pull with
> =E2=80=9C--cores=3D1=E2=80=9D to update their own Guix.

You could also run guix-daemon with --cores=3D4 or similar, so that it
uses 4 cores by default (few package builds scale beyond that anyway),
and then maybe --max-jobs=3D4 so you don=E2=80=99t waste the other cores.  =
;-)

Ludo=E2=80=99.