diff options
| author | 2020-05-26 23:02:29 -0700 | |
|---|---|---|
| committer | 2020-05-29 21:45:06 +0000 | |
| commit | 104d9eb54a668eb87e5c5ada079a0c8b28ba74f4 (patch) | |
| tree | 4ed68626a252d8d29d1a84f438301c9d3b43a917 /sdk/java_sdk_test.go | |
| parent | 42ffc3f0002d64d82449485dfb6572140d268d49 (diff) | |
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 570a292bab2ae73b3338c86cf5836606074adb39)
Diffstat (limited to 'sdk/java_sdk_test.go')
0 files changed, 0 insertions, 0 deletions