Serializing possibly resource-intensive tasks such as meinproc

[Oswald Buddenhagen]

On Fri, Jan 08, 2010 at 04:09:27PM +0100, Lubos Lunak wrote:
> On Thursday 07 of January 2010, Oswald Buddenhagen wrote:
> > for one, covering just meinproc is a bit shortsighted (i bet a few
> > webkit links can blow your box just as nicely :D).
> 
> They can't, because I don't run into 20 webkit links at the same time.
>
well, that was an extreme case. a lower-mem box will blow with fewer,
smaller libraries.
20 uics, (auto-)mocs, etc. are all not nice, either. they might not blow
the ram, but they slow down the rest of the system enough to be
annoying.

> And since icecream currently serializes down to one task even if the
> machine has more cores, I don't want to cover more than what's
> necessary.
> 
this sounds like a nice thing to fix then. ;)
the daemon knows how many local jobs it may run, you just need to use
that value.
note however that *something* is borked in the scheduling. on a small
farm (i.e., two single-core machines, each 2 jobs max) i get waiting
compile jobs and still idle machines pretty often. when i "overrate"
them for 3 jobs max, i usually get them saturated.

> > a more generic solution would be recognizing a KDE4_TOOL_WRAPPER cmake
> > variable and prepending it to all non-c-compiler executables.
> 
>  How about the attached patch then?
> 
+0.5 ;)