From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: Re: llvm on aarch64 builds very slowly
Date: Wed, 23 Feb 2022 17:33:42 +0100 [thread overview]
Message-ID: <877d9lbkll.fsf@elephly.net> (raw)
In-Reply-To: <87wnhmbhpy.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Guix,
>
> I had to manually run the build of llvm 11 on aarch64, because it would
> keep timing out:
>
> time guix build /gnu/store/0hc7inxqcczb8mq2wcwrcw0vd3i2agkv-llvm-11.0.0.drv --timeout=999999 --max-silent-time=999999
>
> After more than two days it finally built. This seems a little
> excessive. Towards the end of the build I saw a 1% point progress
> increase for every hour that passed.
>
> Is there something wrong with the build nodes, are we building llvm 11
> wrong, or is this just the way it is on aarch64 systems?
I now see that gfortran 10 also takes a very long time to build. It’s
on kreuzberg (10.0.0.9) and I see that out of the 16 cores only *one* is
really busy. Other cores sometimes come in with a tiny bit of work, but
you might miss it if you blink.
Guix ran “make -j 16” at the top level, but the other make processes
that have been spawned as children do not have “-j 16”. There are
probably 16 or so invocations of cc1plus, but only CPU0 seems to be busy
at 100% while the others are at 0.
What’s up with that?
--
Ricardo
next prev parent reply other threads:[~2022-02-23 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 23:22 llvm on aarch64 builds very slowly Ricardo Wurmus
2022-02-23 16:33 ` Ricardo Wurmus [this message]
2022-02-23 17:49 ` Christopher Baines
2022-02-26 16:54 ` Kaelyn
2022-02-24 2:23 ` Maxim Cournoyer
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=877d9lbkll.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.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.