update the default # of cores requested in a swarming task |
||||
Issue descriptionI believe that by default we do not ask for a certain number of cores when scheduling a swarming task, and that means that we may end up getting a machine that is not up to the task. See bug 708977 for an example, where we were trying to run browser_tests on a single CPU instance. There are lots of things we could or should do here (like require tasks to specify a minimum or preferred set, etc.) but the simplest fix is at least to overprovision by default and make sure we get into the main pool of 8-core machines.
,
Apr 16 2017
,
Apr 17 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 17 2018
It's 2018. I'm pretty sure we have sufficiently beefy machines in the pool:Chrome, and all the specialty single-core bots have been moved into their own pools. Archiving. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dpranke@chromium.org
, Apr 12 2017