Re: thread priority ?

Vladimir Tzankov writes:

 > Supply/demand is common problem but playing with thread priorities is the
 > wrong way to handle it.
 > Better approach is to do it applications level - e.g. priority queues with
 > thread pools.

I'm having trouble figuring out exactly what you have in mind here.
Priority queues means that within one queue only one thing at a time
is going on, I suppose.  I don't think I understand the thread pools.
It's not expensive to create and destroy threads, is it?
So how do you detect that there's excess capacity and you should 
therefore allow another thread?  And if you detect the reverse, what
do you do about that?

 > Also there are differences how OS-es implement thread priorities
 > (even between releases) - I don't think there is a way to have
 > consistent behaviour.

That sounds like a problem, all right.
Where can I find descriptions of particular behaviors, say, of linux
versions?  Is there some normal "range" of behaviors that's easy to
describe?

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list