all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Mark H Weaver <mhw@netris.org>
Cc: 57788@debbugs.gnu.org
Subject: [bug#57788] [PATCH] gnu: rust: Disable debug info to reduce build requirements
Date: Fri, 7 Oct 2022 13:36:08 +0300	[thread overview]
Message-ID: <Y0ABGL/cobN/iYl4@3900XT> (raw)
In-Reply-To: <874jxahlpi.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

On Tue, Sep 13, 2022 at 07:56:46PM -0400, Mark H Weaver wrote:
> The following patch, which I've tested only on my private branch of
> Guix, dramatically reduces the amount of memory and time required to
> build Rust.
> 
> With this patch applied, I'm able to build Rust on a Thinkpad X200 with
> only 4 GB of RAM using both cores.  Without it, I'm unable to build Rust
> at all, even with parallel builds disabled, running in a bare text-only
> terminal, and with every nonessential daemon stopped.  When I tried, a
> single compiler process used more than 9 GB of virtual memory with heavy
> thrashing before the OOM killer finally put it out of its misery.

Your x200 is an x86_64? How much RAM+swap did you end up using with this
patch? I was going to point you to a patch upstream in mrustc but I
can't find it now, where they disabled debug builds by default, but I
can't find it now.

> Moreover, with this patch the builds are dramatically faster than I've
> previously observed.  In my earlier bootstraps of Rust (up to
> rust-1.51), it took about 5 hours to build each compiler on my machine.
> Now it takes only about 2 hours per compiler, except for the initial
> bootstrap (1.54) which takes about 4 hours.

I tested it out on my machine, it brought the build time down from 101
minutes to 71 minutes. Not the same improvement, but still noticeable.

> The following patch is meant to be applied to the 'staging' branch, but
> I've only tested it on my own private branch, which is based on very old
> 'master' (April 2021) and is thus quite different by now.
> 
> I offer it here in case it might be of interest, although it hasn't been
> tested on contemporary Guix.  I'm not subscribed to this mailing list,
> so please make sure to CC me on any replies you'd like me to see.
> 
>      Regards,
>        Mark

I'm building out to librsvg on staging right now with this patch
applied, so hopefully we'll see that it's good.

I'm assuming that setting CARGO_PROFILE_DEV_DEBUG to false won't cause
any problems.


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-10-07 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 23:56 [bug#57788] [PATCH] gnu: rust: Disable debug info to reduce build requirements Mark H Weaver
2022-10-07 10:36 ` Efraim Flashner [this message]
2022-10-07 22:04   ` Mark H Weaver
2022-10-12 10:45     ` Efraim Flashner
2022-10-28 10:40       ` Mark H Weaver
2022-10-29 19:39         ` Efraim Flashner
2022-11-01  5:11           ` Mark H Weaver
2022-11-01  5:13           ` bug#57788: " Mark H Weaver
2022-10-09 12:38   ` [bug#57788] " Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y0ABGL/cobN/iYl4@3900XT \
    --to=efraim@flashner.co.il \
    --cc=57788@debbugs.gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.