From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#38167: guix pull takes over 8 GiB of memory to finish if there are no substitutes Date: Fri, 27 Dec 2019 19:08:48 +0100 Message-ID: <875zi1hc9b.fsf@gnu.org> References: <20191111080635.14f7b39a@scratchpost.org> <87eeyec18l.fsf@cbaines.net> <878somno0f.fsf@gnu.org> <20191226204555.1abe4d21@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52643) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iku2z-0004RJ-5j for bug-guix@gnu.org; Fri, 27 Dec 2019 13:09:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iku2v-00074U-Ov for bug-guix@gnu.org; Fri, 27 Dec 2019 13:09:12 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:51801) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iku2o-000718-Jn for bug-guix@gnu.org; Fri, 27 Dec 2019 13:09:04 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iku2o-00009a-GL for bug-guix@gnu.org; Fri, 27 Dec 2019 13:09:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20191226204555.1abe4d21@scratchpost.org> (Danny Milosavljevic's message of "Thu, 26 Dec 2019 20:45:55 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 38167@debbugs.gnu.org Hi! Danny Milosavljevic skribis: > On Mon, 11 Nov 2019 21:42:24 +0100 > Ludovic Court=C3=A8s wrote: > >> Also, it would be great if you could identify which derivation build >> requires that much memory, if this was happening sequentially. (I >> suspect =E2=80=9Cguix-packages.drv=E2=80=9D is the one that eats up the = most memory.) > > How do I do that? You could look at the output of =E2=80=9Cguix processes=E2=80=9D and find o= ut which session child process is consuming memory. > I've attached the process tree, filtered by "grep guix", of the latest su= ch > occurence (if this E-Mail still makes it before I have no memory left :P). AFAICS this excludes the actual build process (which runs =E2=80=9Cguile=E2= =80=9D, not =E2=80=9Cguix=E2=80=9D). HTH! Ludo=E2=80=99.