… | |
… | |
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 | } |
… | |
… | |
780 | 479 vfork+execs per second, using AnyEvent::Fork->new_exec |
796 | 479 vfork+execs per second, using AnyEvent::Fork->new_exec |
781 | |
797 | |
782 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
798 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
783 | though it uses the same operations, but adds a lot of overhead? |
799 | though it uses the same operations, but adds a lot of overhead? |
784 | |
800 | |
785 | The difference is simply the process size: forking the 6MB process takes |
801 | The difference is simply the process size: forking the 5MB process takes |
786 | so much longer than forking the 2.5MB template process that the overhead |
802 | so much longer than forking the 2.5MB template process that the extra |
787 | introduced is canceled out. |
803 | overhead introduced is canceled out. |
788 | |
804 | |
789 | If the benchmark process grows, the normal fork becomes even slower: |
805 | If the benchmark process grows, the normal fork becomes even slower: |
790 | |
806 | |
791 | 1340 new processes, manual fork in a 20MB process |
807 | 1340 new processes, manual fork of a 20MB process |
792 | 731 new processes, manual fork in a 200MB process |
808 | 731 new processes, manual fork of a 200MB process |
793 | 235 new processes, manual fork in a 2000MB process |
809 | 235 new processes, manual fork of a 2000MB process |
794 | |
810 | |
795 | What that means (to me) is that I can use this module without having a |
811 | What that means (to me) is that I can use this module without having a bad |
796 | very bad conscience because of the extra overhead required to start new |
812 | conscience because of the extra overhead required to start new processes. |
797 | processes. |
|
|
798 | |
813 | |
799 | =head1 TYPICAL PROBLEMS |
814 | =head1 TYPICAL PROBLEMS |
800 | |
815 | |
801 | This section lists typical problems that remain. I hope by recognising |
816 | This section lists typical problems that remain. I hope by recognising |
802 | them, most can be avoided. |
817 | them, most can be avoided. |
803 | |
818 | |
804 | =over 4 |
819 | =over 4 |
805 | |
820 | |
806 | =item "leaked" file descriptors for exec'ed processes |
821 | =item leaked file descriptors for exec'ed processes |
807 | |
822 | |
808 | POSIX systems inherit file descriptors by default when exec'ing a new |
823 | POSIX systems inherit file descriptors by default when exec'ing a new |
809 | process. While perl itself laudably sets the close-on-exec flags on new |
824 | process. While perl itself laudably sets the close-on-exec flags on new |
810 | file handles, most C libraries don't care, and even if all cared, it's |
825 | file handles, most C libraries don't care, and even if all cared, it's |
811 | often not possible to set the flag in a race-free manner. |
826 | often not possible to set the flag in a race-free manner. |
… | |
… | |
831 | libraries or the code that leaks those file descriptors. |
846 | libraries or the code that leaks those file descriptors. |
832 | |
847 | |
833 | Fortunately, most of these leaked descriptors do no harm, other than |
848 | Fortunately, most of these leaked descriptors do no harm, other than |
834 | sitting on some resources. |
849 | sitting on some resources. |
835 | |
850 | |
836 | =item "leaked" file descriptors for fork'ed processes |
851 | =item leaked file descriptors for fork'ed processes |
837 | |
852 | |
838 | Normally, L<AnyEvent::Fork> does start new processes by exec'ing them, |
853 | Normally, L<AnyEvent::Fork> does start new processes by exec'ing them, |
839 | which closes file descriptors not marked for being inherited. |
854 | which closes file descriptors not marked for being inherited. |
840 | |
855 | |
841 | However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer |
856 | However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer |
… | |
… | |
850 | |
865 | |
851 | The solution is to either not load these modules before use'ing |
866 | The solution is to either not load these modules before use'ing |
852 | L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay |
867 | L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay |
853 | initialising them, for example, by calling C<init Gtk2> manually. |
868 | initialising them, for example, by calling C<init Gtk2> manually. |
854 | |
869 | |
855 | =item exit runs destructors |
870 | =item exiting calls object destructors |
856 | |
871 | |
857 | This only applies to users of Lc<AnyEvent::Fork:Early> and |
872 | This only applies to users of L<AnyEvent::Fork:Early> and |
858 | L<AnyEvent::Fork::Template>. |
873 | L<AnyEvent::Fork::Template>, or when initialiasing code creates objects |
|
|
874 | that reference external resources. |
859 | |
875 | |
860 | When a process created by AnyEvent::Fork exits, it might do so by calling |
876 | When a process created by AnyEvent::Fork exits, it might do so by calling |
861 | exit, or simply letting perl reach the end of the program. At which point |
877 | exit, or simply letting perl reach the end of the program. At which point |
862 | Perl runs all destructors. |
878 | Perl runs all destructors. |
863 | |
879 | |
… | |
… | |
882 | to make it so, mostly due to the bloody broken perl that nobody seems to |
898 | to make it so, mostly due to the bloody broken perl that nobody seems to |
883 | care about. The fork emulation is a bad joke - I have yet to see something |
899 | care about. The fork emulation is a bad joke - I have yet to see something |
884 | useful that you can do with it without running into memory corruption |
900 | useful that you can do with it without running into memory corruption |
885 | issues or other braindamage. Hrrrr. |
901 | issues or other braindamage. Hrrrr. |
886 | |
902 | |
887 | Cygwin perl is not supported at the moment, as it should implement fd |
903 | Cygwin perl is not supported at the moment due to some hilarious |
888 | passing, but doesn't, and rolling my own is hard, as cygwin doesn't |
904 | shortcomings of its API - see L<IO::FDPoll> for more details. |
889 | support enough functionality to do it. |
|
|
890 | |
905 | |
891 | =head1 SEE ALSO |
906 | =head1 SEE ALSO |
892 | |
907 | |
893 | L<AnyEvent::Fork::Early> (to avoid executing a perl interpreter), |
908 | L<AnyEvent::Fork::Early> (to avoid executing a perl interpreter), |
894 | L<AnyEvent::Fork::Template> (to create a process by forking the main |
909 | L<AnyEvent::Fork::Template> (to create a process by forking the main |