<div dir="ltr">All,<div><br></div><div>While we discussed many other things, we also discussed about reducing time taken for the regression jobs. As it stands now, it take around 5hr 40mins to complete a single run.</div><div><br></div><div>There were many suggestions:</div><div><br></div><div><ul><li>Run them in parallel (as each .t test is independent of each other)</li><li>Revisit the tests taking long time (20 tests take almost 6000 seconds as of now).</li><li>See if we can run the tests in docker (but the issue is the machines we have are of 2cores, so there may not be much gain)</li></ul><div><br></div></div><div>There are other suggestions as well:</div><div><br></div><div><ul><li>Spend effort and see if there are repeated steps, and merge the tests.</li><ul><li>Most of the time is spent in starting the processes and cleaning up.</li><li>Most of the tests run the similar volume create command (depending on the volume type), and run few different type of I/O in different tests.</li><li>Try to see if these things can be merged.</li><li>Most of the bug-fix .t files belong to this category too.</li></ul><li>Classify the tests specific to few non-overlapping volume types and depending on the changeset in the patch (based on the files changed) decide which are the groups to run. </li><ul><li>For example, you can't have replicate and disperse volume type together.</li></ul></ul><div><br></div></div><div>---- </div><div><br></div><div>More ideas and suggestions welcome.</div><div><br></div><div><br></div><div>Regards,</div><div>Amar</div><div><div><br></div>
</div></div>