[ViewVC] Diff of: cvs/Coro-Multicore/perlmulticore.h

Comparing Coro-Multicore/perlmulticore.h (file contents):
Revision 1.3 by root, Sat Jun 27 19:38:59 2015 UTC vs.
Revision 1.4 by root, Sat Jun 27 19:47:45 2015 UTC

 first are two memory accesses and a predictable function call of an empty
 function.
 Of course, the overhead is much higher when these functions actually
 implement anything useful, but you always get what you pay for.
+With L<Coro::Multicore>, every release/acquire involves two pthread
+switches, two coro thread switches, a bunch of syscalls, and sometimes
+interacting with the event loop.
+A dedicated thread pool such as the one L<IO::AIO> uses could reduce
+these overheads, and would also reduce the dependencies (L<AnyEvent> is a
+smaller and more portable dependency than L<Coro>), but it would require a
+lot more work on the side of the module author wanting to support it than
+this solution.
 =item Low Code and Data Size Overhead
 On a 64 bit system, F<perlmulticore.h> uses exactly C<8> octets (one
 pointer) of your data segment, to store the C<perl_multicore_api>

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines