I think what Jordan is exploring, and I agree on, is that we need clear
next steps to help reduce the 75% ish increase in dtest runtime. For
sponsored contributors using circle to run the entire suites, throwing more
money at the problem through parallelization isn't a long-term solution.
On Sat,
I know the dtests take a long time and this will make them longer. As a counter
point most people run individual dtests locally and the full set on dedicated
test infrastructure. For the dedicated test infrastructure Mick also improved
the wall clock runtime when parallelizing the dtests on
htt
