Our infrastructure at Mozilla does a great job of supporting all the jobs we 
need to run jobs for the thousands of pushes we do each month.  Currently Talos 
runs on real hardware (and we have no plans to change that), but it does mean 
that we have a limited pool of available machines.  Right now this isn't a 
problem for Linux 32 or 64 since we don't run any other jobs on those platforms.

The problem we do have is on OSX and Windows, and in the last 2 weeks we have 
had a big problem with backlog on Windows.  The main reason we have a problem 
on OSX and Windows is because we run all the unit tests on there as well.  
Granted we have a larger pool of machines, but we run a considerably larger 
volume of tests on there.

Trying to be smart about what we are doing, bug 1204920 [1] was filed to look 
into what would happen if we stopped running Talos on Linux32.  We would still 
have OSX, Windows, and Linux64 support and from looking at all the data for the 
last 90 days, there are very few minor differences between 32 and 64 when it 
comes to catching regressions.

After looking into this, we realized that we could reimage the linux32 machines 
as windows machines- this would then solve our backlog and give us some 
breathing room on capacity until we find other ways to reduce the load or make 
a more formal decision to increase the machine pool.

Sadly there are really no plans to formally add back Linux32 support.  What 
does Linux32 give us that Linux64 doesn't when it comes to Talos results?  I am 
looking at this from a narrow lens, quite possibly someone else has ideas of 
what might be more useful.  Overall we are serious about doing this, but want 
to do it knowing more so at what cost.

Thanks for reading and fixing Performance regressions when they show up in your 
patches!


[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1204920
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to