Closed Bug 696959 Opened 13 years ago Closed 13 years ago

set up two more test masters for osx slaves

Categories

(Release Engineering :: General, defect, P5)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jhford, Unassigned)

References

Details

(Whiteboard: [capacity][waittimes])

These are to handle the added load of the talos-r4 machines. roughly, we can handle 80 unix slaves per test master. This should block putting 10.7 testers into production and repurposing the rev3 10.6 machines.
Depends on: 696964
Summary: set up two more unix test masters → set up two more test masters for unix slaves
We now have 2 linux specific masters, leaving three masters that are ostensibly osx specific masters. Lets see how wait times are before setting up even more masters bm04-tests1 bm06-tests1 bm11-tests1 bm15-tests1-windows bm16-tests1-windows bm17-tests1-linux bm18-tests1-linux test-master01
Summary: set up two more test masters for unix slaves → set up two more test masters for osx slaves
looking at the wait time email from Oct 29, it looks like we are handling the load of 80 rev4 machines along with 100 rev3 machines just fine on three masters. leopard: 2011 0: 1990 98.96% snowleopard: 2016 0: 1972 97.82% snowleopard-r4: 2014 0: 2001 99.35% Snowleopard is going to go away and its machines will begin supplementing non-osx platforms. As these are on different master pools, I think we should be able to handle the net increase of 30 rev4 lion machines. For now, lets just set 4,6,11 aside for osx and reevaluate putting more masters in the OS X pool once we have 80 more 10.7 machines.
Severity: major → normal
Depends on: 698568
Priority: -- → P5
the load averages on bm04,06,11 is looking like its averaging 0.8 to 1.0. We might need one more master for the lion machines.
We are doing OK on master load after adding the two linux masters and moving all linux load to them.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.