← Back to team overview

yellow team mailing list archive

Re: Timings from data center

 

This is great news.

So roughly 10m + 19m + 265m/workers. Neato.

Testr will ignore the layers if you configure the new option we added;
it will still show a layer that fails to startup. This may help with
the idle time aspect.

What do you think of us getting say 16cores, hyperthreaded, *one*
machine. That would make the action from idle snappier, at the cost of
either contention when there are serial landings, or complexity in
buildbot to say 'only run one test at a time, devel || db-devel'.

Relatedly, ec2land - do you think the HVM instance would be cost
effective for ec2land/ec2 test? It sounds like it has great results @
36 minutes, but perhaps just an 8 core is sufficiently good @ 51
minutes?

Ideally we'd have a super fast environment totally spun up and devs
could reuse it individually, reducing setup cost and really tuning
things; I think that is something for the next pass - definitely out
of scope for this project. (It probably needs to be in canonistack, it
probably needs N-machine scaling at that point, and other non-trivial
additional works.

-Rob


Follow ups

References