Re: [boost] Boost.Fiber review January 6-15

Subject: Re: [boost] Boost.Fiber review January 6-15
From: james (james_at_[hidden])
Date: 2014-01-12 04:13:34

On 11/01/2014 18:51, Oliver Kowalke wrote:
> 2014/1/11 james<james_at_[hidden]>
>
>> >Given that a blocking system call is poisonous to throughput of all the
>> >fibres
>> >on a thread
>> >
> I would try to prevent blocking system calls (at least set the NONBLOCK
> option) and use
> boost.asio instead (if possible).
>
> _______________________________________________
> Unsubscribe & other changes:http://lists.boost.org/mailman/listinfo.cgi/boost
That's not in any realistic way feasible.  It might do for home-grown 
code that
works on sockets directly, but you will be out of luck with almost any third
party database library or anything else that wraps up communication or
persistence in any way.  It also impacts code that uses libraries that have
data structures protected by locks that might be held for extended periods
sometimes.  Most of these will be more important to a project than 
fibres, or
indeed boost.