<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 11, 2016 at 4:19 PM, David Caro <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@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"><div id=":1ar" class="">You are not having into account yet that we are not using most of the hardware<br>
we have yet, that will allow us to have more than twice the amount of slaves we<br>
have now too (given that we solve any other bottleneck, like nfs storage)</div></blockquote></div><br></div><div class="gmail_extra">I agree. I think best thing to begin with would be to add as many slaves<br></div><div class="gmail_extra">as we can and remove all restrictions from the jobs and monitor the queue.<br></div><div class="gmail_extra"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Last time we tried using it, it ended messing up all the executions, mixing<br>
slaves and creating a lot of failures, if you try it out, be very vigilant</blockquote><div>good to know <br></div></div></div>