<html>#536: Don't overload machines while building
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>As of git hash <a data-is-external-link="true" href="https://bitbucket.org/simfactory/simfactory2/commits/6576596959b854d80582f581876313f039386944" rel="nofollow">6576596</a> "wheeler: use makejobs" of <a data-is-external-link="true" href="https://bitbucket.org/simfactory/simfactory2" rel="nofollow">simfactory2</a> most (all?) machines in simfactory support a <code>-j</code> switch on the level of simfactory making it easy for users to choose how many parallel make jobs to use.</p>
<p>It does not quite automatically pick the correct value but makes it straightforward to control this. Since <code>-l</code> seems to not really work and implementing locks will only allow per user limits (and not take into account activity of other users) and is typically fragile, I will close this as wontfix.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/536/dont-overload-machines-while-building'>https://bitbucket.org/einsteintoolkit/tickets/issues/536/dont-overload-machines-while-building</a></p>
</html>