From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#27284: Memory leak in 'guix pull' or 'make' in guix source Date: Mon, 13 Nov 2017 15:09:00 +0100 Message-ID: <87lgjatgn7.fsf@elephly.net> References: <20170608083935.izw747zaetkaxv4o@abyayala> <87poamv2i7.fsf@gnu.org> <87375jchbu.fsf@gnu.org> <87shdituzk.fsf@elephly.net> <87vaiebk8d.fsf@gnu.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:4830:134:3::10]:47182) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eEFS7-00041P-Si for bug-guix@gnu.org; Mon, 13 Nov 2017 09:11:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eEFS2-0007Yh-Qx for bug-guix@gnu.org; Mon, 13 Nov 2017 09:11:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57430) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eEFS2-0007Xs-NV for bug-guix@gnu.org; Mon, 13 Nov 2017 09:11:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87vaiebk8d.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 27284@debbugs.gnu.org Ludovic Court=C3=A8s writes: >> I was hoping we could avoid this, but whatever: let=E2=80=99s do this :) > > Yeah, me too. The problem we have is that Guix is hardly releasable in > its current state because on systems with 1GiB of memory you can=E2=80=99= t > upgrade, and I think that=E2=80=99s unacceptable. Yes, I=E2=80=99m feeling the pain with my i686 netbook. > So what are the options? If we get a bug-fix for Guile=E2=80=99s compile= r > today, does it help? If we graft it then we can deliver it without > having to wait for a Guile release, which helps a bit? > > I think it=E2=80=99s all about time: we could wait (and hack!) some more,= and > solve the root problem. This is the best long-term course of action, > but at the same time it delays the Guix release. The way I see it, having very large modules like (gnu packages python) is not desirable anyway. So we won=E2=80=99t get around distributing packa= ge definitions. If we can get a fix for Guile soon that=E2=80=99s great, but = we should begin moving packages independent of that. >> For haskell.scm I=E2=80=99d begin by moving the following packages away: >> >> - check.scm: ghc-tasty*, ghc-quickcheck*, ghc-test*, ghc-hunit*, hspec*, >> ghc-hspec*, =E2=80=A6 >> >> - web.scm: ghc-tagsoup, ghc-cookie, ghc-http*, ghc-wai*, ghc-json, >> ghc-warp*, ghc-multipart, ghc-aeson* >> >> - crypto.scm: ghc-tf-random, ghc-digest, ghc-cryptonite, ghc-x509*, >> ghc-asn1*, ghc-pem, ghc-cryptohash*, ghc-entropy, ghc-crypto-api*, >> ghc-puremd5 >> >> - tls.scm: ghc-tls >> >> Maybe that=E2=80=99s enough already. >> >> Does that seem like a good idea? > > It does. Okay, I=E2=80=99ll get started with splitting haskell.scm. I=E2=80=99ll pr= epare one patch for each target module. > Actually, we could do similarly for Perl and Python: > python-web, python-check, python-crypto, etc. Okay. I=E2=80=99ll leave that task for someone else, because I don=E2=80= =99t think I can do more than haskell.scm today. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net