… | |
… | |
27 | |
27 | |
28 | Special care has been taken to make this module useful from other modules, |
28 | Special care has been taken to make this module useful from other modules, |
29 | while still supporting specialised environments such as L<App::Staticperl> |
29 | while still supporting specialised environments such as L<App::Staticperl> |
30 | or L<PAR::Packer>. |
30 | or L<PAR::Packer>. |
31 | |
31 | |
32 | =head1 WHAT THIS MODULE IS NOT |
32 | =head2 WHAT THIS MODULE IS NOT |
33 | |
33 | |
34 | This module only creates processes and lets you pass file handles and |
34 | This module only creates processes and lets you pass file handles and |
35 | strings to it, and run perl code. It does not implement any kind of RPC - |
35 | strings to it, and run perl code. It does not implement any kind of RPC - |
36 | there is no back channel from the process back to you, and there is no RPC |
36 | there is no back channel from the process back to you, and there is no RPC |
37 | or message passing going on. |
37 | or message passing going on. |
… | |
… | |
40 | in whatever way you like, use some message-passing module such |
40 | in whatever way you like, use some message-passing module such |
41 | as L<AnyEvent::MP>, some pipe such as L<AnyEvent::ZeroMQ>, use |
41 | as L<AnyEvent::MP>, some pipe such as L<AnyEvent::ZeroMQ>, use |
42 | L<AnyEvent::Handle> on both sides to send e.g. JSON or Storable messages, |
42 | L<AnyEvent::Handle> on both sides to send e.g. JSON or Storable messages, |
43 | and so on. |
43 | and so on. |
44 | |
44 | |
|
|
45 | =head2 COMPARISON TO OTHER MODULES |
|
|
46 | |
|
|
47 | There is an abundance of modules on CPAN that do "something fork", such as |
|
|
48 | L<Parallel::ForkManager>, L<AnyEvent::ForkManager>, L<AnyEvent::Worker> |
|
|
49 | or L<AnyEvent::Subprocess>. There are modules that implement their own |
|
|
50 | process management, such as L<AnyEvent::DBI>. |
|
|
51 | |
|
|
52 | The problems that all these modules try to solve are real, however, none |
|
|
53 | of them (from what I have seen) tackle the very real problems of unwanted |
|
|
54 | memory sharing, efficiency, not being able to use event processing or |
|
|
55 | similar modules in the processes they create. |
|
|
56 | |
|
|
57 | This module doesn't try to replace any of them - instead it tries to solve |
|
|
58 | the problem of creating processes with a minimum of fuss and overhead (and |
|
|
59 | also luxury). Ideally, most of these would use AnyEvent::Fork internally, |
|
|
60 | except they were written before AnyEvent:Fork was available, so obviously |
|
|
61 | had to roll their own. |
|
|
62 | |
45 | =head1 PROBLEM STATEMENT |
63 | =head2 PROBLEM STATEMENT |
46 | |
64 | |
47 | There are two traditional ways to implement parallel processing on UNIX |
65 | There are two traditional ways to implement parallel processing on UNIX |
48 | like operating systems - fork and process, and fork+exec and process. They |
66 | like operating systems - fork and process, and fork+exec and process. They |
49 | have different advantages and disadvantages that I describe below, |
67 | have different advantages and disadvantages that I describe below, |
50 | together with how this module tries to mitigate the disadvantages. |
68 | together with how this module tries to mitigate the disadvantages. |
… | |
… | |
212 | open my $output, ">/tmp/log" or die "$!"; |
230 | open my $output, ">/tmp/log" or die "$!"; |
213 | |
231 | |
214 | AnyEvent::Fork |
232 | AnyEvent::Fork |
215 | ->new |
233 | ->new |
216 | ->eval (' |
234 | ->eval (' |
|
|
235 | # compile a helper function for later use |
217 | sub run { |
236 | sub run { |
218 | my ($fh, $output, @cmd) = @_; |
237 | my ($fh, $output, @cmd) = @_; |
219 | |
238 | |
220 | # perl will clear close-on-exec on STDOUT/STDERR |
239 | # perl will clear close-on-exec on STDOUT/STDERR |
221 | open STDOUT, ">&", $output or die; |
240 | open STDOUT, ">&", $output or die; |
… | |
… | |
351 | use AnyEvent; |
370 | use AnyEvent; |
352 | use AnyEvent::Util (); |
371 | use AnyEvent::Util (); |
353 | |
372 | |
354 | use IO::FDPass; |
373 | use IO::FDPass; |
355 | |
374 | |
356 | our $VERSION = 0.5; |
375 | our $VERSION = 0.6; |
357 | |
|
|
358 | our $PERL; # the path to the perl interpreter, deduces with various forms of magic |
|
|
359 | |
376 | |
360 | =over 4 |
377 | =over 4 |
361 | |
378 | |
362 | =back |
379 | =back |
363 | |
380 | |
… | |
… | |
442 | if ($pid eq 0) { |
459 | if ($pid eq 0) { |
443 | require AnyEvent::Fork::Serve; |
460 | require AnyEvent::Fork::Serve; |
444 | $AnyEvent::Fork::Serve::OWNER = $parent; |
461 | $AnyEvent::Fork::Serve::OWNER = $parent; |
445 | close $fh; |
462 | close $fh; |
446 | $0 = "$_[1] of $parent"; |
463 | $0 = "$_[1] of $parent"; |
447 | $SIG{CHLD} = 'IGNORE'; |
|
|
448 | AnyEvent::Fork::Serve::serve ($slave); |
464 | AnyEvent::Fork::Serve::serve ($slave); |
449 | exit 0; |
465 | exit 0; |
450 | } elsif (!$pid) { |
466 | } elsif (!$pid) { |
451 | die "AnyEvent::Fork::Early/Template: unable to fork template process: $!"; |
467 | die "AnyEvent::Fork::Early/Template: unable to fork template process: $!"; |
452 | } |
468 | } |