build: Tweak linker memory usage for android static build

build/toolchain/concurrent_links.gni

 # Copyright 2016 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This file should only be imported from files that define toolchains.
 # There's no way to enforce this exactly, but all toolchains are processed
 # in the context of the default_toolchain, so we can at least check for that.
 assert(current_toolchain == default_toolchain)
 
 import("//build/config/sanitizers/sanitizers.gni")
@@ skipping 10 matching lines @@
 if (concurrent_links == -1) {
   if (allow_posix_link_time_opt || is_cfi) {
     _args = [
       "--mem_per_link_gb=24",
       "--reserve_mem_gb=10",
     ]
   } else if (is_win) {
     _args = [ "--mem_per_link_gb=5" ]
   } else if (is_mac) {
     _args = [ "--mem_per_link_gb=4" ]
+  } else if (is_android && !is_component_build) {
+    _args = [ "--mem_per_link_gb=25" ]

[Dirk Pranke, 2016/08/26 17:50:45]

is this number correct for both debug and release? it's a big change, so if we
want to land this as-is you need to make sure we make sure cycle time goes down,
not up :).

[boliu, 2016/08/26 17:58:16]

this was measured when I copied the config from the official release bots, so
definitely not debug.

I thought debug+static build isn't a thing anymore though?

I'm guessing the next config that matters most is symbol_level, and 25G is
measured at symbol_level=2. I could measure 1 and 0 if you want?

   } else {
     _args = []
   }
 
   # TODO(crbug.com/617429) Pass more build configuration info to the script
   # so that we can compute better values.
   concurrent_links = exec_script("get_concurrent_links.py", _args, "value")
 }