AOSP Compile Time

[vzl...@gmail.com]

Hi everyone,

I'm interacted on the compiling time for AOSP project in different systems.

If you have the time to share some results about building time and you system information to be a reference for anyone please do.

I will start:

AOSP: Android 11

CPU: i7-8550U

RAM: 32G and 16G swap

Disk: HDD

Time for full clean compile: 6~7h

For me there is huge bottleneck because the HDD.

[William Durham]

With a SN550 1tb nvme home directory and 500gb nvme for my out directory, core i5 10600k, 32gb ram, from a fresh sync, no ccache, its 2hrs or so here

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/016992b7-4834-4ebf-9bc6-b77a1b7b13b0n%40googlegroups.com.

[Dan Willemsen]

Most of the time you probably should be doing incremental builds instead of clean builds (it's very rare to see incremental build issues anymore), so clean build numbers should be somewhat less important than they used to be. If you're interested in diving into your build's performance, we've got some documentation at build/soong/docs/perf.md

I'll post some numbers tomorrow about what we see at Google, but a few more important pieces of information for anyone sharing:

• What branch you checked out (master around X date, android tagged release, etc)
• Which product and variant you're building (aosp_arm64-userdebug can be very different from aosp_arm-eng, others can be even more different)
• What you're building (`m sync` is faster than `m [droid]` which is faster than `m dist`)
• Any other options you may be providing to the build (there are options to turn on code coverage analysis, clang-tidy, errorprone, etc -- all of these add more work)

Even with the same source tree and machine, you can easily get at least a 2-3x spread in build times with different products, targets, and options.

- Dan

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAKBspjzjk5XORjhsF_UNghJ6Fa7%3DwCHO%2BBisY-Gn7d2r8aZ4qg%40mail.gmail.com.

[Adarsh K]

I built lineage os 18 on my potato pc with

R3 3200G(4C 4T) 

16GB RAM

500GB Nvme

In 6 hrs. 

I gave 16GB SWAP but it barely used 3GB

Like you said, that HDD you use is a huge bottleneck. 

[Eduardo Soares de Moraes]

Hi there.

are you using a notebook or some other laptop? I'm sure HDD (NVME or IDE/SATA) doesn't make much difference. switch to a processor that does not end in a "U"

I recommend doing clean builds only once a month or every time you change something really important. incremental builds are enough.

• hideki