From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: parallelizing more actions
Date: Thu, 16 Nov 2017 11:06:09 +0100 [thread overview]
Message-ID: <871skyilm6.fsf@gnu.org> (raw)
In-Reply-To: <20171113185522.GM1815@macbook41> (Efraim Flashner's message of "Mon, 13 Nov 2017 20:55:22 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Sun, Nov 12, 2017 at 03:31:49PM +0200, Efraim Flashner wrote:
>> On Thu, Nov 09, 2017 at 11:05:59AM +0200, Efraim Flashner wrote:
>> > While rebuilding glibc-final on aarch64 I realized that the 'strip phase
>> > took 235 seconds. The relevant code for 'strip from gnu-build-system is
>> > in guix/build/gnu-build-system.scm, starting at line 340, with the
>> > actual stripping starting at 398. When I changed 'for-each' to
>> > 'par-for-each' the time dropped from 235 seconds to 215, about an 8.5%
>> > savings. I'm pretty sure most of that time was spent failing to strip
>> > certain files, but it is still a savings.
>> >
>>
>> These numbers were for glibc@2.26. I ran it against glibc@2.25 on my
>> x86_64 machine with a spinning harddrive and 2 cores, without the patch
>> it took 165.7 seconds (164.6 the second time), with the patch it dropped
>> to 24.3 seconds.
>>
>> I'll test it with glibc@2.25 on aarch64 later when its not building
>> other things.
>>
>
> Looks like aarch64 could use some help somewhere. With the patch it took
> 221.9 seconds, without the patch it was 219.8.
>
> so in summary, aarch64 is terrible at stripping, parallel or not, and on
> x86_64 my patch saved 85% of the patching time, despite only using 2 cores.
This is weird. I don’t see any reason why ‘strip’ would be slower on
aarch64 than elsewhere. Are you sure it’s not mostly I/O? It would be
nice to time it and see the real/user/system times.
Thanks,
Ludo’.
prev parent reply other threads:[~2017-11-16 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:05 parallelizing more actions Efraim Flashner
2017-11-11 1:42 ` Chris Marusich
2017-11-11 11:25 ` Ludovic Courtès
2017-11-11 16:49 ` Efraim Flashner
2017-11-12 13:31 ` Efraim Flashner
2017-11-13 18:55 ` Efraim Flashner
2017-11-16 10:06 ` Ludovic Courtès [this message]
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=871skyilm6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--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.