Page MenuHomePhabricator

Consider increasing number of trusty CI slaves
Closed, ResolvedPublic

Assigned To
Authored By
Legoktm
Feb 10 2016, 8:11 AM
Referenced Files
F3334488: graph-2.png
Feb 11 2016, 10:27 PM
F3330950: graph.png
Feb 10 2016, 9:50 PM
F3330915: Selection_102.png
Feb 10 2016, 9:23 PM
F3330913: Selection_101.png
Feb 10 2016, 9:23 PM

Description

Now that php53 is no longer run for master, most changes will only trigger jobs that run on trusty slaves. I am slightly concerned that we don't have enough trusty slaves, when I was triggering all MW extensions, all trusty executor slots were constantly filled. That was a total edge case, so we should probably monitor it for a few days and see if we're running out of capacity.

Event Timeline

Legoktm raised the priority of this task from to Needs Triage.
Legoktm updated the task description. (Show Details)
Legoktm added subscribers: Legoktm, hashar.
Krinkle claimed this task.
Krinkle subscribed.

@hashar and I just created half a dozen Trusty slaves to supply for the new demand of php55/trusty jobs.

Visual representation of what happened:

Selection_101.png (404×834 px, 70 KB)

and
Selection_102.png (468×992 px, 27 KB)

Thank you very much @Krinkle to have stepped in and help grow out the Trusty pool. I myself completely missed the work stress the php53 -> php55 would have caused :-\

The good news: we need less Precise slaves!

6 instances have been pooled. They are labs flavor ci.medium (2 CPU, 2GB RAM, 40GB disk). Each have been added with two executors.

A view for the associated Jenkins label illustrate the number of executors being added. Graph is only on a short period of time so does not reflect the original situation, but really we went from 32 slots to 44.

graph.png (500×992 px, 39 KB)

The ci.medium flavor turned out to lack memory so we got m1.large instance instead. Report at T126545#2020702

Last 24 hours view for UbuntuTrusty:

graph-2.png (500×740 px, 49 KB)

Looks fine now.