Reduce DefaultConcurrentLinks from phys/4GB to phys/5GB.
Reduce DefaultConcurrentLinks from phys/4GB to phys/5GB.

This is copied from the gyp repo, ninja.py:
https://codereview.chromium.org/1255813005

VS 2015 uses about 20% more memory when linking. This caused a
severe page-fault storm on my development machine and subsequent tests
showed that linking could use ~63 GB of RAM (15 parallel links on a
64 GB machine). This suggests that VS 2013 would also be using a lot
of RAM (52.5 GB?) such that very little was left for other
applications or disk cache.

Linker working sets vary wildly but with VS 2013 there are six links
that use over 6 GB of working set and with VS 2015 there are seven.

This change reduces parallel links by 20% (increase RAM-per-linker by
25%). The value can be overridden by setting GYP_LINK_CONCURRENCY.

Tests with VS 2013 showed no statistically significant change in
build times when link concurrency was reduced from 15 to 10 or 12.
Further reductions may be prudent when we switch to VS 2015.

BUG=440500
R=brettw@chromium.org

Review URL: https://codereview.chromium.org/1261073004

Cr-Commit-Position: 972c6d2dc6dd5efdad1377c0d224e03eb8f276f7@{#342892}

ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,ltilve/ChromiumGStreamerBackend,CapOM/ChromiumGStreamerBackend