Re: [Boost-users] Thread_group semantics

Subject: Re: [Boost-users] Thread_group semantics
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2014-01-13 17:39:32

Le 13/01/14 23:21, Kenneth Adam Miller a écrit :
> So, suppose that I give so many tasks to a thread_group that it 
> becomes more than what the thread pool can handle. I would want the 
> thread pool to just take longer, but still complete them all. Also, I 
> want the tasks processed First Come First Serve. What happens when too 
> many tasks are given to it? Do they get queued up?
>
thread_group stores threads not tasks. In addition it is deprecated. I'm 
working on a basic thread pool in the develop branch. Boost.1.55 
contains a first implementation but not yet documented in 
https://github.com/boostorg/thread/blob/master/include/boost/thread/thread_pool.hpp, 
but the interface will surely change when released 
https://github.com/boostorg/thread/blob/develop/include/boost/thread/executors/basic_thread_pool.hpp.

HTH,
Vicente
>
> On Mon, Jan 13, 2014 at 1:01 AM, Gavin Lambert <gavinl_at_[hidden] 
> <mailto:gavinl_at_[hidden]>> wrote:
>
>     On 9/01/2014 23:40, Quoth Kenneth Adam Miller:
>
>         When a thread_group is assigned a task using post, does that
>         task get
>         executed sequentially? Is there a list, so that, when too many
>         posts are
>         added to it, it keeps track of them?
>
>
>     Can you rephrase the question?  boost::thread_group does not have
>     a post method.
>
>
>     _______________________________________________
>     Boost-users mailing list
>     Boost-users_at_[hidden] <mailto:Boost-users_at_[hidden]>
>     http://lists.boost.org/mailman/listinfo.cgi/boost-users
>
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users