Use 32 cores machines for LUCI perf tester |
||
Issue descriptionWe want to swap out all 8 cores LUCI perf tester with 32 cores to improve the speed of uploading (also see issue 857283). Since we don't have any 32 cores machine left, I plan to switch android-arm64-builder-perf which is using 18 32-cores machines to use 32 8-core machines instead. I has confidence that this should work because: *Building android-arm64 with 8 cores take about ~33 minutes in https://ci.chromium.org/buildbot/chromium.perf/Android%20arm64%20Compile%20Perf/ * Building android with 8 cores take about 10 minutes, and only require 10 bots to fill all the Chromium commit load. * so by tripling the number of bots building android, we should be able to use 8 cores for building android-arm64 Doing this will give us 18 32-cores Linux machines back, which should be more than enough to fill all the Linux perf testers.
,
Aug 30
Using 32 cores machine helped! Now the uploading on linux takes 5.5 minutes (https://logs.chromium.org/logs/chrome/buildbucket/cr-buildbucket.appspot.com/8936744655125223888/+/steps/performance_test_suite_on_Android_device_Pixel_2/0/logs/Merge_script_log/0) instead of 15 minutes (https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf.fyi%2Fandroid-pixel2-perf%2F1322%2F%2B%2Frecipes%2Fsteps%2Fperformance_test_suite_on_Android_device_Pixel_2%2F0%2Flogs%2FMerge_script_log%2F0)
,
Aug 30
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Aug 30