Measuring infrastructure load for Feb 2009

The data for January on the volume of changes (see here, and here) was quite useful, so here is the data for February.

In February, people pushed 940 code changes into the mercurial-based repos here in Mozilla. That is slightly lower then last month, but then again, February is a shorter month, and there’s been a prolonged freeze for FF3.1b3.

As each of these pushes triggers multiple different types of builds/unittest jobs, the *theoretical* total amount of work done by the pool-of-slaves in February was 9,559 jobs. For each push, we do:

  • mozilla-central: 11 jobs per push (L/M/W opt, L/M/W leaktest, L/M/W unittest, linux64 opt, linux-arm)
  • mozilla-1.9.1: 10 jobs per push (L/M/W opt, L/M/W leaktest, L/M/W unittest, linux64 opt)
  • tracemonkey: 7 jobs per push (L/M/W opt, L/M/W unittest, linux64 opt)
  • theoretical total: (579 x 11) + (221 x 10) + (140 x 7) = 9,559 jobs. Or an average of 14.2 jobs per hour for the month. (Considering how many of our jobs take over an hour to complete, this is quite scary!)

Hopefully people find this is interesting, its certainly useful for RelEng as we try to make sure we have enough machines to keep up.

2 thoughts on “Measuring infrastructure load for Feb 2009

  1. There are a small number of nightly builds each day too, 4 each for m-c and m-1.9.1 and 3 for tracemonkey, and a lot of l10n builds. Just in case you wanted to break the 9600 barrier ๐Ÿ™‚ Of course it would be interesting to know how many jobs the slaves actually did, to get a handle on how much changeset merging is going on.