Re: [android-building] Soong regenerate after any Android.bp change slow

[Michael Swartout]

Lucky yours only takes 60 seconds. It takes 18 minutes, everytime I make a change to almost anything.

On Wed, Feb 1, 2023 at 9:29 PM Dean Wheatley <dw...@dolby.com> wrote:

Is there a better/faster way to develop Android.bp in the AOSP tree than waiting for the many (> 60) seconds it takes to "analyzing Android.bp files and generating ninja file at out/soong/build.ninja" after any change to any Android.bp file in the tree?

--
--
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/e19325ce-2798-4d80-8de8-b0312c7bb69an%40googlegroups.com.

[enh]

(yeah, anecdotally "about a minute" sounds about right for the
machines developers at google have. i've seen 2-3 minutes too.)

> To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAEq4fyCTGiHjboJaFXnBbN_kBTJwjOvuWoTg_-7D%3Dx6Qq3c7UA%40mail.gmail.com.

[Dean Wheatley]

Wow, 18 minutes, that's unbearable.

[Dean Wheatley]

Any hints from Googlers on how to improve this?

[enh]

yeah, unfortunately i'm only aware of two options, and they're both basically "throw money at the problem until it goes away":

1. get a better computer. (256 GiB of ram, 64 cores, and 2 TiB of ssd are the current default.)

2. build in the cloud. https://cs.android.com/android/platform/superproject/+/master:build/soong/docs/rbe.md has some details, but i'm not sure there's a step-by-step guide anywhere.

(google actually uses _both_ together, so although i can personally vouch for "1 without 2" as useful and "1 and 2" as useful, i've never tried "2 without 1".)

On Tue, Mar 14, 2023 at 8:26 AM Michael Swartout <michaelc...@gmail.com> wrote:

I overcame that issue, changing 18 minutes into 3 minutes now. By changing my 24gb of memory that was only 2400mhz., into 32gb of memory at 3200mhz. And it was unbearable for me also. Soong only analyzes after certain things you do in the source code. For sure, after a mk or or bp file change. It won't do it if you have compiled a library or libraries already and it is a dependency of the library or binary you are trying to currently compile.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/6c196f08-e689-4163-ba8c-cc517a100eb4n%40googlegroups.com.

--
--
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/CAEq4fyDkKBJUdqeQ2W2n7m1jJWsNJpGOgMDvLgq86og7_Sb%2BMw%40mail.gmail.com.

[Michael Swartout]

You purchased way to much, overkill.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAJgzZor%2Bpj%2BmrNqR2fKRNGkNwmBbzxUtzQZaVOhar19EMrC6gQ%40mail.gmail.com.

[enh]

depends how much you value your time. we have graphs somewhere where we actually did the experiment of adding memory and cores. iirc the impact of more memory does top out somewhere around 128GiB, but since everything grows and 256 is the next step up, that gives some breathing room to keep these machines useful. (similarly with disk space, though it's always easier to add disk space after the fact than it is memory.)

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAEq4fyCBa3oOtT-7p-SVMnMgQCrheuu%3D_p1bu9vgt8E_pUG0Qw%40mail.gmail.com.

[Christopher Nugent]

I feel you. I splurged on a Threadripper Pro 24-core machine with 128 GB of RAM and 960 GB Intel optane source code storage drive because I wanted to spend what I could afford to minimize the time I spend waiting for Android ROM builds.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CAJgzZor8ctD4N30nqgWpwFxZoJe71A0mgRH9Oqm5FVcu32RGSQ%40mail.gmail.com.

[洪归风]

Can you reduce compile times simply by upgrading to faster memory? I'm encountering a similar issue where it takes about 10 minutes to generate the ninja file. I currently have 64GB of memory, but it's running at a speed of only 2133MHz. Therefore, I'm wondering if I should upgrade my memory or my CPU.

在2023年3月14日星期二 UTC+8 23:26:05<Michael Swartout> 写道：

I overcame that issue, changing 18 minutes into 3 minutes now. By changing my 24gb of memory that was only 2400mhz., into 32gb of memory at 3200mhz. And it was unbearable for me also. Soong only analyzes after certain things you do in the source code. For sure, after a mk or or bp file change. It won't do it if you have compiled a library or libraries already and it is a dependency of the library or binary you are trying to currently compile.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/6c196f08-e689-4163-ba8c-cc517a100eb4n%40googlegroups.com.

[enh]

i'd guess upgrading your cpu would have more benefit --- but note that
more threads is more important than single-core performance.

> To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/7e8f2c99-c95b-4768-b0f2-00481a31b716n%40googlegroups.com.