Re: Tasks unleashed

[Jano <nono@celes.unizar.es>]

tmoran@acm.org dice...
> >In any case, the memory thing forces to use pools of reusable tasks,
> >it's my main and crucial conclusion.
> 
>   Have you considered a protected Buffer of work to do and a fixed pool of
> tasks which queue on an entry waiting for the Buffer to have some work to
> do (or instructions to quit)?  Then you needn't create or destroy the
> worker tasks.

That's exactly what I'm doing :) but sometimes the "fixed" compromise 
bugs me. ITOH, normally is better to have a upper bound for things, I 
think.

-- 
-------------------------
Jano
402450.at.cepsz.unizar.es
-------------------------