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

Issue 870865 link

Starred by 2 users
Status: Fixed
Owner:
qyears...@chromium.org
Closed: Aug 13
Cc:
█ smut@chromium.org
mar...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 871456



Sign in to add a comment

Scale up Tricium pool for chromium/src

Project Member Reported by qyears...@chromium.org, Aug 3 
The tricium pool now seems to be mostly or all busy most of the time, and most of the tasks appear to be for CLs in chromium/src.

Currently there are seem to be 10 bots in the tricium pool (listed at https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&f=os%3AUbuntu&f=cpu%3Ax86&f=pool%3Atricium) but in the project "tricium-bots" there are 12 bots listed. 2 of them say they can't be used because quota for CPUs is exceeded (max 24 CPUs per region).

As far as I understand, more bots could be created if the quota was increased or each bot was changed to use fewer CPUs. Is that how this works?

Comment 1 by qyears...@chromium.org, Aug 3 

Compute engine suggested changing VM templates from "4 vCPUs, 3.6 GB" with "2 vCPUs, 3.75 GB" since it says some tasks are running low on memory; this would also make each bot use fewer CPUs, thus allowing more bots to be created without changing quota. Now trying that out.

Comment 2 by qyears...@chromium.org, Aug 3

Labels: -Pri-3 Pri-1
Owner: qyears...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by qyears...@chromium.org, Aug 3 

Note, original tricium pool was set up in https://crbug.com/778330

Comment 4 by qyears...@chromium.org, Aug 3 

So, it turns out that I shouldn't have messed with GCE instances, instance groups, or instance templates in GCE itself, I should have changed the config somewhere else.

Comment 5 by qyears...@chromium.org, Aug 4 

The config change should have been in the gce-backend configs (managers.cfg and templates.cfg).

Comment 6 by qyears...@chromium.org, Aug 6

Blocking: 871456

Comment 7 by qyears...@chromium.org, Aug 6

Status: Started (was: Assigned)
At present, the tricium pool seems to have capacity, but we still should probably increase capacity (made a CL).
Project Member

Comment 8 by bugdroid1@chromium.org, Aug 7 

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

commit 96e4efe0c1e446c259153bc0095d3cdee17e8b79
Author: Quinten Yearsley <qyearsley@chromium.org>
Date: Tue Aug 07 19:08:08 2018

Comment 9 by qyears...@chromium.org, Aug 7

Cc: smut@chromium.org
Summary: Scale up Tricium pool for chromium/src (was: Scale up Tricium pool for chromium/src?)
Status update: the current state is that the pool appears to be partly idle, but there are ~136 pending tasks. The queue started building up around 11:30, before the above commit was committed.
Project Member

Comment 10 by bugdroid1@chromium.org, Aug 8 

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

commit e64a116e8e2fb96ee6b19db4400904ccfe61537f
Author: Quinten Yearsley <qyearsley@chromium.org>
Date: Wed Aug 08 15:04:49 2018
Project Member

Comment 11 by bugdroid1@chromium.org, Aug 9 

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

commit 10f4971a90f4aded61fab155d241ce7ceaa2c53c
Author: smut <smut@google.com>
Date: Thu Aug 09 23:33:13 2018

Comment 12 by qyears...@chromium.org, Aug 13

Status: Fixed (was: Started)
Project Member

Comment 13 by bugdroid1@chromium.org, Aug 16 

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

commit ade521667ea54965cc7b2a0c99e24eb915eed787
Author: smut <smut@google.com>
Date: Thu Aug 16 00:34:04 2018
►

Sign in to add a comment