Re: Threadpool with priority version 1.1 ...

[Warren <ve3wwg@gmail.com>]

Maciej Sobczak expounded in news:7794a413-34e9-4340-abcc-a6568246fc38
@h18g2000yqo.googlegroups.com:

> On 24 Mar, 17:40, Warren <ve3...@gmail.com> wrote:
> 
>> Another barrier I see to this is the high cost of
>> starting a new thread and stack space allocation.
> 
>> Somehow you gotta make thread startup and shutdown
>> cheaper.
> 
> Why?
> 
> The problem of startup/shutdown cost and how many cores you have are
> completely orthogonal.
> I see no problem in starting N threads at the initialization time, use
> them throughout the application lifetime and then shut down at the end
> (or never)...

I forgot to mention that the disadvantage of this approach is that
you have to "pre-allocate" stack space for each thread (whether
by default amount or by a specific designed amount).

If you used a true cactus stack, this is not an issue. But with a 
traditional thread, you could choose stack requirements at the 
point of thread creation. Not so, if you create them all up front.

So there are downsides to this approach.

Warren