New issue
Advanced search Search tips

Issue 681190 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Swap elm-paladin (build115-m2) and beaglebone-paladin (build100-m2)

Project Member Reported by dgarr...@chromium.org, Jan 13 2017

Issue description

snanda:

elm-paladin is typically the slowest paladin and usually takes 10-15 minutes more than the next slowest paladin.  Looking closer, the build slave it runs on (build115-m2) is much less powerful (32 cores @2.6Ghz) than the one (build100-m2: 40 cores @3Ghz) that beaglebone runs on.

Could we swap the builders between elm-paladin & beaglebone?  That might shave off 10-15 minutes per CQ run.
 
Can we just swap them in the json file that shows which builder is assigned to what, and then wait for the next waterfall restart?
Cc: semenzato@chromium.org

Comment 3 by autumn@chromium.org, Jan 17 2017

Labels: -current-issue

Comment 4 by snanda@chromium.org, Jan 18 2017

dnj: any thoughts on how we go about swapping the elm & beaglebone paladin builders?
This was hopefully fixed as part of  crbug.com/682400  which moved the elm-paladin to a GCE beefy instance.

Comment 7 by snanda@chromium.org, Jan 20 2017

Woah!  That's awesome.  Now we can look at the next set of slowest builders and see what can be done about them.
I'm about to try and fix  crbug.com/682789 , which will get rid of the last of our slowest build machines, but poppy is on GCE, so it won't help there.

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 10 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 12 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment