Chromium Code Reviews| Index: tools/gn/scheduler.cc |
| diff --git a/tools/gn/scheduler.cc b/tools/gn/scheduler.cc |
| index a711df1cf02b41ed43cfff7b1bc1e5eaccc67da5..664a086be45753ac283ac0140b711db547a7fbe1 100644 |
| --- a/tools/gn/scheduler.cc |
| +++ b/tools/gn/scheduler.cc |
| @@ -54,10 +54,13 @@ int GetThreadCount() { |
| // |
| // One less worker thread than the number of physical CPUs seems to be a |
| // good value, both theoretically and experimentally. But always use at |
| - // least three workers to prevent us from being too sensitive to I/O latency |
| + // least some workers to prevent us from being too sensitive to I/O latency |
| // on low-end systems. |
| + // |
| + // The minimum thread count is based on the optiman threads for the Chrome |
|
Nico
2016/05/06 21:33:51
typo (or super hero?) optiman
|
| + // build on a several-year-old 4-core MacBook |
| int num_cores = GetCPUCount() / 2; // Almost all CPUs now are hyperthreaded. |
| - return std::max(num_cores - 1, 3); |
| + return std::max(num_cores - 1, 8); |
| } |
| } // namespace |