The minimum requirements for the build is 16GB of RAM available (and even with that it can be difficult later in the build). The virtualization mention was meant to say that a machine with 16GB of RAM wasn't enough when virtualizing -- the virtual machine would need 16GB allocated to it.
`m -j1` means that we'll only launch a single process at a time, but many of those spin up a number of threads on their own. Parallelism can have some effect on peak RAM use, but I wouldn't expect that to significantly affect things, at least for soong_build. Which target you're building can have a reasonably big impact on RAM usage (as 64-bit targets need both 64 and 32 bit configurations). On my machine with aosp-master: aosp_cf_x86_phone - soong_build peaks at ~6GB (and allocated ~20GB over its lifetime). next, kati takes ~4GB aosp_crosshatch - soong_build peaks at ~8.5GB (and allocated ~26GB over its lifetime). next, kati takes ~6GB For some of our larger branches/targets, I've seen peaks at >14GB (~50GB lifetime allocs), with kati using >10GB. - Dan On Thu, Apr 30, 2020 at 12:05 PM Eliane Fonseca <[email protected]> wrote: > same problem with 2 processes and I have only 8 GB of physical RAM and it > is not virtualized system . any timing for fix ? > > Em 30 de abr de 2020 13:43, "Silver Rampart" <[email protected]> > escreveu: > > When running a normal build, process soong_build quickly fills up all > available memory (6GB in under 5 minutes) and starts to swap. Quad-core i5. > I understand this might have something to do with parallelism, but I run > make with -j1 and soong_build is still running multiple threads. > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/android-building/ca25a692-cd1f-4096-be61-552017644208%40googlegroups.com > <https://groups.google.com/d/msgid/android-building/ca25a692-cd1f-4096-be61-552017644208%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/android-building/CAJ%2BSQK6ow5BwiNHUpt9bxTcjnJsyVBptX6mkL%2B4Pn9KaA3mNRA%40mail.gmail.com > <https://groups.google.com/d/msgid/android-building/CAJ%2BSQK6ow5BwiNHUpt9bxTcjnJsyVBptX6mkL%2B4Pn9KaA3mNRA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CALQgHdnkEefTzYxU%2BYnGH5RN27vROLmBitc6VkfgVCwjLMuN3g%40mail.gmail.com.
