Re: Threadpool with priority version 1.1 ...

[Maciej Sobczak <see.my.homepage@gmail.com>]

On 26 Mar, 09:19, "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de>
wrote:

> BTW, if this approach worked for an application, it should also do for the
> OS,

It is true, obtaining resources up-front requires more careful
analysis of the problem that is being solve and is not always
possible.
The difference between application and OS is in the amount of
knowledge about what the software will do and applications tend to
know more than OS in this aspect.
That is why it is more realistic to have applications allocating their
resources during initialization phase than to see that at the OS
level.

I'm not a big fan of programs that allocate and deallocate the same
resource repeatedly - this is an obvious candidate for caching and
object reuse, where the cost of allocation is amortized. Fortunately,
it is not even necessary for a user code to do that - think about a
caching memory allocator, there are analogies. And the language
standard does not prevent implementations from reusing physical
threads, if they are used as implementation foundations for tasks.

--
Maciej Sobczak * http://www.inspirel.com

YAMI4 - Messaging Solution for Distributed Systems
http://www.inspirel.com/yami4