Closed Bug 584289 Opened 16 years ago Closed 15 years ago

Rebalance 10.6 builder minis between production and try pools to match load

Categories

(Release Engineering :: General, defect, P3)

x86_64
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Unassigned)

References

Details

(Whiteboard: [buildslaves][slaveduty])

I'm filing this in RelEng while we sort out how many machines to upgrade, and if we should rebalance the moz2 and try pools. This will get moved to Server Ops when that is decided. To get us started: * we have 40 Snow Leopard machines in the moz2 pool. Since 2010-07-13 we have at most 20 concurrent builds running across all branches in that pool. * we have 26 Snow Leopard machines in the try pool. Since 2010-07-13 we have at most 25 concurrent builds running, four times above 20. This suggests to me that we should upgrade all the machines we have, and split them 30/36 between moz2/try (10 above the peak on each pool). I'd like to check what proportion of those jobs are tests, since those have mostly moved to the minis. And we also have another 10 machines which already have 2G of RAM which can be re-purposed from 10.5 based builds (assuming load is OK there). Would appreciate your input Messrs Catlee and Hearsum.
bug#584820 filed to purchase 3gb ram for each of 81 minis being used as osx10.6 builder.
Depends on: 584820
This bug was about 2 topics a) upgrading ram on 10.6 builder minis, and b) rebalancing builder pools to match workload. As IT are doing the ram upgrades in bug#584820, I've morphed this bug to just be about the remaining "rebalance pools" work, which is a RelEng task.
Summary: Upgrade RAM in 10.6 minis to 2G → Rebalance 10.6 builder minis between production and try pools to match load
On the most recent heavy day on try, Fri 8 Oct, we did snowleopard: 123 0: 121 98.37% 15: 2 1.63% The previous day on non-try, we did snowleopard: 105 0: 105 100.00% so there isn't any issue at the moment.
Assignee: nrthomas → nobody
Priority: P2 → P3
Shall we close this and file a new one if needed?
(In reply to comment #3) > On the most recent heavy day on try, Fri 8 Oct, we did > snowleopard: 123 > 0: 121 98.37% > 15: 2 1.63% > > The previous day on non-try, we did > snowleopard: 105 > 0: 105 100.00% > > so there isn't any issue at the moment. Cool. (In reply to comment #4) > Shall we close this and file a new one if needed? Yep.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [buildslaves] → [buildslaves][slaveduty]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.