llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Maksim Panchenko <maks@fb.com>
Cc: android-llvm-dev <android-llvm-dev@google.com>,
	 android-kernel-team <android-kernel-team@google.com>,
	Yi Kong <yikong@google.com>,
	 clang-built-linux <llvm@lists.linux.dev>
Subject: Initial LLVM+BOLT measurements
Date: Wed, 20 Apr 2022 10:41:52 -0700	[thread overview]
Message-ID: <CAKwvOdm08hr2p-ARqmPEGnCi6zZOtgmt5d45hYG2vo30mhyMrg@mail.gmail.com> (raw)

Hi Maksim,
Just letting you know that my teammate Yi just enabled the usage of
BOLT on AOSP LLVM. [0] There are some speedups measured in building
the Android platform.

I'm more interested in kernel builds; here's some rough (N=1) initial
measurements to report:

r450784b:
$ LTO=none BUILD_CONFIG=common/build.config.gki.aarch64 /usr/bin/time
-v ./build/build.sh
...
        Elapsed (wall clock) time (h:mm:ss or m:ss): 1:58.58
$ BUILD_CONFIG=common/build.config.gki.aarch64 /usr/bin/time -v ./build/build.sh
...
        Elapsed (wall clock) time (h:mm:ss or m:ss): 16:50.04

r450784c:
$ $ LTO=none BUILD_CONFIG=common/build.config.gki.aarch64
/usr/bin/time -v ./build/build.sh
...
        Elapsed (wall clock) time (h:mm:ss or m:ss): 1:50.64
$ BUILD_CONFIG=common/build.config.gki.aarch64 /usr/bin/time -v ./build/build.sh
        Elapsed (wall clock) time (h:mm:ss or m:ss): 16:06.56

(We care more about the LTO (longer) config than non-LTO). So rough
initial measurement shows improvement of ~6.6% (non-LTO) to ~4.3%
(LTO). We'll take it! :)

[0] https://android-review.googlesource.com/c/toolchain/llvm_android/+/2058849/
-- 
Thanks,
~Nick Desaulniers

                 reply	other threads:[~2022-04-20 17:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAKwvOdm08hr2p-ARqmPEGnCi6zZOtgmt5d45hYG2vo30mhyMrg@mail.gmail.com \
    --to=ndesaulniers@google.com \
    --cc=android-kernel-team@google.com \
    --cc=android-llvm-dev@google.com \
    --cc=llvm@lists.linux.dev \
    --cc=maks@fb.com \
    --cc=yikong@google.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).