<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 5, 2016 at 9:59 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> Here are builds that do not change the build system:<br>
> - <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5767/console" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>vdsm_master_check-patch-fc24-<wbr>x86_64/5767/console</a>:<br>
> 10:07<br>
> - <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/4157/console" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>vdsm_master_check-patch-el7-<wbr>x86_64/4157/console</a>:<br>
> 10:16<br>
><br>
> So we about 2X times faster now.<br>
<br>
</span>Awesome! also for fc24:<br>
<br>
22:11:22 Init took 73 seconds<br>
<br>
22:13:45 Install packages took 143 seconds<br>
<br>
So 3m 36s, our pending patches can probably bring that down to around<br>
20s. That will get us to around 7m...<br>
Maybe we could shave some more seconds off by optimizing the git clone<br>
and making some of the cleanups happen less frequently.<br>
(It seems we spend 16s total outside of mock_runner.sh, so perhaps not<br>
much to gain there).<br>
<br>
So any more ideas where we can get extra 2-3m?<br></blockquote><div><br></div><div>Can we run the tests in parallel in nose[1] ?</div><div>Y.</div><div><br></div><div>[1] <a href="http://nose.readthedocs.io/en/latest/doc_tests/test_multiprocess/multiprocess.html">http://nose.readthedocs.io/en/latest/doc_tests/test_multiprocess/multiprocess.html</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Things we didn`t try yet:<br>
1. Ensure all downloads happen through the proxy (there is a patch<br>
pending, but some tweaking in check_patch.sh may be needed as well)<br>
2. Run mock in tmpfs (it has a plugin for that)<br>
3. Avoid setting some FS attributes on files (mock is configured for<br>
that but we don't install the OS package needed to make that actually<br>
work)<br>
<br>
Nut sure any of the above will provide significant gains though.<br>
<span class="gmail-im gmail-HOEnZb"><br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHCE, RHCi, RHV-DevOps Team<br>
<a href="https://ifireball.wordpress.com/" rel="noreferrer" target="_blank">https://ifireball.wordpress.<wbr>com/</a><br>
</span><div class="gmail-HOEnZb"><div class="gmail-h5">______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br></div></div>