On 09/12/2012 09:33 AM, Hans de Graaff wrote: > On Wed, 2012-09-12 at 08:58 -0400, Ian Stakenvicius wrote: > >> So essentially what you're saying here is that it might be worthwhile >> to look into parallelism as a whole and possibly come up with a >> solution that combines 'emerge --jobs' and build-system parallelism >> together to maximum benefit? > > Forget about jobs and load average, and just keep starting jobs all > around until there is only 20% (or whatever tuneable amount) free memory > left. As far as I can tell this is always the real bottleneck in the > end. Once you hit swap overall throughput has to go down quite a bit.
Well, I think it's still good to limit the number of jobs at least, since otherwise you could become overloaded with processes that don't consume a lot of memory at first but by the time they complete they have consumed much more memory than desired (using swap). -- Thanks, Zac
