Does Boost 1.56 boost::async support auto scheduling (launch deferred)?
Hi, Onc of the design choices for async() default launch policy was to allow the OS scheduler to decide whether or not to launch a new thread or remain on the same thread (presumably based on available system resources). Does Boost 1.56 or 1.57 support this default auto scheduling yet? It seems to be launching as many threads as tasks. Thanks, Adi
Le 01/12/14 08:15, Adi Shavit a écrit :
Hi,
Onc of the design choices for async() default launch policy was to allow the OS scheduler to decide whether or not to launch a new thread or remain on the same thread (presumably based on available system resources). Does Boost 1.56 or 1.57 support this default auto scheduling yet? No, not yet. This is a QOI issue. I 'm not sure the documentation defines this behavior. Anyway, could you add a Trac ticket so that I don't forget to think about on how this can be achieved. It seems to be launching as many threads as tasks.
Right. Best, Vicente
Vicente J. Botet Escriba <vicente.botet <at> wanadoo.fr> writes:
Does Boost 1.56 or 1.57 support this default auto scheduling yet? No, not yet. This is a QOI issue. I 'm not sure the documentation defines this behavior. Anyway, could you add a Trac ticket so that I don't forget to think about on how this can be achieved.
participants (3)
-
Adi Shavit -
Vicente J. Botet Escriba