Platform/2010-08-03: Difference between revisions

 
Line 110: Line 110:
** Try server pushes are consistently taking 13-14 hours from push to last result email.  Try server does not *appear* to be under heavier load than m-c (push rate eyeballs about the same); why is there such a huge difference?
** Try server pushes are consistently taking 13-14 hours from push to last result email.  Try server does not *appear* to be under heavier load than m-c (push rate eyeballs about the same); why is there such a huge difference?
*** Try push load for July is ~65% higher than mozilla-central
*** Try push load for July is ~65% higher than mozilla-central
*** Test or build requests cannot be consolidated together on try
*** Build or test requests cannot be consolidated together on try, but can be consolidated during peak load on mozilla-central.
*** All builds on TryServer are full-clobber builds, not incremental builds like on mozilla-central
*** No fast build machines for try.  Shuffling from mozilla-central and other project branches would slow those down.
*** No fast build machines for try.  Shuffling from mozilla-central and other project branches would slow those down.
*** If we ordered new hardware today, it would be at least 4 weeks to be racked up, installed, etc.  No hardware has been ordered as yet.
*** If we ordered new hardware today, it would be at least 4 weeks to be racked up, installed, etc.  No hardware has been ordered as yet.
*** Not all available testing slaves are currently enabled due to snow-ball effect during high jobs load. {{bug|563458}}
*** Not all available testing slaves are currently enabled due to snow-ball effect during high jobs load. {{bug|563458}}
Confirmed users
2,679

edits