Il 11/09/2012 18:43, Zac Medico ha scritto:
On 09/11/2012 09:36 AM, viv...@gmail.com wrote:
Dunno where to place this request, but if we go for something like EJOBS
could we also make it phase specific?
So compile, install and test could have a different number of jobs running.
Possibly three different variables that override a predefined EJOBS.
Per-phase sounds a little to fine-grained. Instead, I'd suggest to add
an ELOADAVG variable that's analogous to make's --load-average option.
That should be enough to compensate for any differences between phases.
ok, but in my experience load-average really is too limited so I
relaunch with the ability to control the following:
- disk io
- network
- memory
- cpu
- jobs
just tough that being able to control just jobs in a phase specific
manner could have been sufficed ;-)
Also this seem is a good job for containers, already implemented in the
linux kernel, but will let someone with experience with them comment on
the mattter.
