Closed Bug 1845320 Opened 1 year ago Closed 1 year ago

Increase Wayland pool's maxCapacity

Categories

(Firefox Build System :: Task Configuration, task)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ahal, Assigned: ahal)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

Now that the pool has scaling in GCE, let's ramp up to allow more than 4 workers.

20 was chosen arbitrarily and will likely be adjusted later.

Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/8a0e62eff0ff Bump up maxCapacity in Wayland pool, r=jmaher
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

I'd like to start doing some larger try pushes to get a better sense of the
overall work. Twenty workers isn't enough to churn through a push in < a day.

Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/9d027d9b6430 Bump up maxCapacity in Wayland pool to 100, r=jmaher,jcristau
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

As we've been adding the more suites, I've noticed several hour long wait times
on some of my try pushes. For comparison, the non-Wayland pool has maxCapacity
set to 2500, but also runs way more tasks. So 500 seems like a reasonable next
step.

Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/e3fee0d63e6b Bump up maxCapacity in Wayland pool to 500, r=releng-reviewers,bhearsum
Status: REOPENED → RESOLVED
Closed: 1 year ago1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: