Files
build_soong/ui/build
Dan Willemsen 104d9eb54a Better handling of low memory situations
Drop down to a single high-mem task when we've got <=16GB, as the system
probably isn't completely free RAM, ninja will be using a couple gigs,
along with whatever "normal" actions will be running concurrently. So
it's unlikely that we can handle two 6-8GB actions along with everything
else.

Also print warnings when we detect <=16GB total RAM, or when we're
running more parallel jobs than than we have GB RAM. These both notify
the user and suggest lowering the `-j` value if they run into problems.

Bug: 141066538
Test: fake totalRAM to [0.5,8,16]GB, checking warning
Test: fake totalRAM to 17GB, `m -j4 nothing` has no warning
Test: `m -j187 nothing` on a 188GB system
Test: `m -j188 nothing` on a 188GB system
Change-Id: Ieb008e9f462d5f40fb65781d94cf116b1caf8446
Merged-In: Ieb008e9f462d5f40fb65781d94cf116b1caf8446
(cherry picked from commit 570a292bab)
2020-05-29 21:45:06 +00:00
..
2020-03-07 11:22:30 -08:00
2019-07-23 16:16:15 -04:00
2020-03-27 12:03:30 +00:00
2019-10-04 12:53:51 -07:00
2019-07-17 18:46:47 +00:00
2017-02-22 10:44:19 -08:00
2018-07-12 14:15:31 -07:00