New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 879159 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 857283



Sign in to add a comment

Use 32 cores machines for LUCI perf tester

Project Member Reported by nednguyen@chromium.org, Aug 30

Issue description

We 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.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 30

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/config/+/ee48317874a798792b293b3c12def90b501d3842

commit ee48317874a798792b293b3c12def90b501d3842
Author: nednguyen <nednguyen@google.com>
Date: Thu Aug 30 16:51:50 2018

Status: Fixed (was: Started)

Sign in to add a comment