
14 Jan
2014
14 Jan
'14
7 p.m.
2014/1/14 Hartmut Kaiser
I'd be disappointed if the overheads imposed by Boost.Fiber are only 2-3 times smaller than for kernel threads. I'd expect it to impose at least 10 times, if not 15-20 times less overheads than kernel threads (at least that's the numbers we're seeing from HPX).
yes - I'm disappointed too. but, as I already explaned, I was focused on boost.asio's async-result and to provide a ways to synchronized coroutiens with an interface similar to std::thread. tuning seams to need more attention from my side - at first I've to identify the bottlenecks.