perf bots take a long time to build |
||||
Issue descriptione.g. android_nexus5_perf_bisect (invoked via "tools/pref/run_benchmark trybot android-nexus5") takes over 45 minutes to do its "compile (with patch)", out of about 75 minutes total runtime. It looks like it does an rmtree of the build directory, and then does a clean build with only -j50. The "without patch" build also runs with these parameters, but at least isn't doing a clobber build. Is it necessary to do a clobber build on this bot (and is there a way I can ask it not to)? Could we use more goma jobs so that this completes faster?
,
Apr 27 2016
e.g. https://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3631 It also seems to build a number of targets not required for the test it's trying to run.
,
Apr 27 2016
,
May 3 2016
,
Jan 18 2017
Pri-3 with no updates in 180+ days that are available and have no owner == Archived. Feel free to update status, add context as to why and move this along. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jbroman@chromium.org
, Apr 27 2016