ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-Fork/Fork.pm
(Generate patch)

Comparing AnyEvent-Fork/Fork.pm (file contents):
Revision 1.47 by root, Thu Apr 18 20:17:34 2013 UTC vs.
Revision 1.59 by root, Fri Aug 30 12:06:48 2013 UTC

38 38
39If you need some form of RPC, you could use the L<AnyEvent::Fork::RPC> 39If you need some form of RPC, you could use the L<AnyEvent::Fork::RPC>
40companion module, which adds simple RPC/job queueing to a process created 40companion module, which adds simple RPC/job queueing to a process created
41by this module. 41by this module.
42 42
43And if you need some automatic process pool management on top of
44L<AnyEvent::Fork::RPC>, you can look at the L<AnyEvent::Fork::Pool>
45companion module.
46
43Or you can implement it yourself in whatever way you like, use some 47Or you can implement it yourself in whatever way you like: use some
44message-passing module such as L<AnyEvent::MP>, some pipe such as 48message-passing module such as L<AnyEvent::MP>, some pipe such as
45L<AnyEvent::ZeroMQ>, use L<AnyEvent::Handle> on both sides to send 49L<AnyEvent::ZeroMQ>, use L<AnyEvent::Handle> on both sides to send
46e.g. JSON or Storable messages, and so on. 50e.g. JSON or Storable messages, and so on.
47 51
48=head2 COMPARISON TO OTHER MODULES 52=head2 COMPARISON TO OTHER MODULES
250 ->send_arg ("/bin/echo", "hi") 254 ->send_arg ("/bin/echo", "hi")
251 ->run ("run", my $cv = AE::cv); 255 ->run ("run", my $cv = AE::cv);
252 256
253 my $stderr = $cv->recv; 257 my $stderr = $cv->recv;
254 258
259=head2 For stingy users: put the worker code into a C<DATA> section.
260
261When you want to be stingy with files, you cna put your code into the
262C<DATA> section of your module (or program):
263
264 use AnyEvent::Fork;
265
266 AnyEvent::Fork
267 ->new
268 ->eval (do { local $/; <DATA> })
269 ->run ("doit", sub { ... });
270
271 __DATA__
272
273 sub doit {
274 ... do something!
275 }
276
277=head2 For stingy standalone programs: do not rely on external files at
278all.
279
280For single-file scripts it can be inconvenient to rely on external
281files - even when using < C<DATA> section, you still need to C<exec>
282an external perl interpreter, which might not be available when using
283L<App::Staticperl>, L<Urlader> or L<PAR::Packer> for example.
284
285Two modules help here - L<AnyEvent::Fork::Early> forks a template process
286for all further calls to C<new_exec>, and L<AnyEvent::Fork::Template>
287forks the main program as a template process.
288
289Here is how your main program should look like:
290
291 #! perl
292
293 # optional, as the very first thing.
294 # in case modules want to create their own processes.
295 use AnyEvent::Fork::Early;
296
297 # next, load all modules you need in your template process
298 use Example::My::Module
299 use Example::Whatever;
300
301 # next, put your run function definition and anything else you
302 # need, but do not use code outside of BEGIN blocks.
303 sub worker_run {
304 my ($fh, @args) = @_;
305 ...
306 }
307
308 # now preserve everything so far as AnyEvent::Fork object
309 # in §TEMPLATE.
310 use AnyEvent::Fork::Template;
311
312 # do not put code outside of BEGIN blocks until here
313
314 # now use the $TEMPLATE process in any way you like
315
316 # for example: create 10 worker processes
317 my @worker;
318 my $cv = AE::cv;
319 for (1..10) {
320 $cv->begin;
321 $TEMPLATE->fork->send_arg ($_)->run ("worker_run", sub {
322 push @worker, shift;
323 $cv->end;
324 });
325 }
326 $cv->recv;
327
255=head1 CONCEPTS 328=head1 CONCEPTS
256 329
257This module can create new processes either by executing a new perl 330This module can create new processes either by executing a new perl
258process, or by forking from an existing "template" process. 331process, or by forking from an existing "template" process.
259 332
377use AnyEvent; 450use AnyEvent;
378use AnyEvent::Util (); 451use AnyEvent::Util ();
379 452
380use IO::FDPass; 453use IO::FDPass;
381 454
382our $VERSION = 0.7; 455our $VERSION = 1.1;
383 456
384# the early fork template process 457# the early fork template process
385our $EARLY; 458our $EARLY;
386 459
387# the empty template process 460# the empty template process
435 # send string 508 # send string
436 my $len = syswrite $self->[FH], $self->[QUEUE][0]; 509 my $len = syswrite $self->[FH], $self->[QUEUE][0];
437 510
438 unless ($len) { 511 unless ($len) {
439 return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; 512 return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK;
440 undef $self->[3]; 513 undef $self->[WW];
441 die "AnyEvent::Fork: command write failure: $!"; 514 die "AnyEvent::Fork: command write failure: $!";
442 } 515 }
443 516
444 substr $self->[QUEUE][0], 0, $len, ""; 517 substr $self->[QUEUE][0], 0, $len, "";
445 shift @{ $self->[QUEUE] } unless length $self->[QUEUE][0]; 518 shift @{ $self->[QUEUE] } unless length $self->[QUEUE][0];
448 521
449 # everything written 522 # everything written
450 undef $self->[WW]; 523 undef $self->[WW];
451 524
452 # invoke run callback, if any 525 # invoke run callback, if any
526 if ($self->[CB]) {
453 $self->[CB]->($self->[FH]) if $self->[CB]; 527 $self->[CB]->($self->[FH]);
528 @$self = ();
529 }
454 }; 530 };
455 531
456 () # make sure we don't leak the watcher 532 () # make sure we don't leak the watcher
457} 533}
458 534
529 605
530You should use C<new> whenever possible, except when having a template 606You should use C<new> whenever possible, except when having a template
531process around is unacceptable. 607process around is unacceptable.
532 608
533The path to the perl interpreter is divined using various methods - first 609The path to the perl interpreter is divined using various methods - first
534C<$^X> is investigated to see if the path ends with something that sounds 610C<$^X> is investigated to see if the path ends with something that looks
535as if it were the perl interpreter. Failing this, the module falls back to 611as if it were the perl interpreter. Failing this, the module falls back to
536using C<$Config::Config{perlpath}>. 612using C<$Config::Config{perlpath}>.
537 613
614The path to perl can also be overriden by setting the global variable
615C<$AnyEvent::Fork::PERL> - it's value will be used for all subsequent
616invocations.
617
538=cut 618=cut
619
620our $PERL;
539 621
540sub new_exec { 622sub new_exec {
541 my ($self) = @_; 623 my ($self) = @_;
542 624
543 return $EARLY->fork 625 return $EARLY->fork
544 if $EARLY; 626 if $EARLY;
545 627
628 unless (defined $PERL) {
546 # first find path of perl 629 # first find path of perl
547 my $perl = $; 630 my $perl = $;
548 631
549 # first we try $^X, but the path must be absolute (always on win32), and end in sth. 632 # first we try $^X, but the path must be absolute (always on win32), and end in sth.
550 # that looks like perl. this obviously only works for posix and win32 633 # that looks like perl. this obviously only works for posix and win32
551 unless ( 634 unless (
552 ($^O eq "MSWin32" || $perl =~ m%^/%) 635 ($^O eq "MSWin32" || $perl =~ m%^/%)
553 && $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i 636 && $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i
554 ) { 637 ) {
555 # if it doesn't look perlish enough, try Config 638 # if it doesn't look perlish enough, try Config
556 require Config; 639 require Config;
557 $perl = $Config::Config{perlpath}; 640 $perl = $Config::Config{perlpath};
558 $perl =~ s/(?:\Q$Config::Config{_exe}\E)?$/$Config::Config{_exe}/; 641 $perl =~ s/(?:\Q$Config::Config{_exe}\E)?$/$Config::Config{_exe}/;
642 }
643
644 $PERL = $perl;
559 } 645 }
560 646
561 require Proc::FastSpawn; 647 require Proc::FastSpawn;
562 648
563 my ($fh, $slave) = AnyEvent::Util::portable_socketpair; 649 my ($fh, $slave) = AnyEvent::Util::portable_socketpair;
571 #local $ENV{PERL5LIB} = join ":", grep !ref, @INC; 657 #local $ENV{PERL5LIB} = join ":", grep !ref, @INC;
572 my %env = %ENV; 658 my %env = %ENV;
573 $env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC; 659 $env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC;
574 660
575 my $pid = Proc::FastSpawn::spawn ( 661 my $pid = Proc::FastSpawn::spawn (
576 $perl, 662 $PERL,
577 ["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$], 663 ["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$],
578 [map "$_=$env{$_}", keys %env], 664 [map "$_=$env{$_}", keys %env],
579 ) or die "unable to spawn AnyEvent::Fork server: $!"; 665 ) or die "unable to spawn AnyEvent::Fork server: $!";
580 666
581 $self->_new ($fh, $pid) 667 $self->_new ($fh, $pid)
582} 668}
583 669
584=item $pid = $proc->pid 670=item $pid = $proc->pid
585 671
586Returns the process id of the process I<iff it is a direct child of the 672Returns the process id of the process I<iff it is a direct child of the
587process running AnyEvent::Fork>, and C<undef> otherwise. 673process running AnyEvent::Fork>, and C<undef> otherwise. As a general
674rule (that you cannot rely upon), processes created via C<new_exec>,
675L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template> are direct
676children, while all other processes are not.
588 677
589Normally, only processes created via C<< AnyEvent::Fork->new_exec >> and 678Or in other words, you do not normally have to take care of zombies for
590L<AnyEvent::Fork::Template> are direct children, and you are responsible 679processes created via C<new>, but when in doubt, or zombies are a problem,
591to clean up their zombies when they die. 680you need to check whether a process is a diretc child by calling this
592 681method, and possibly creating a child watcher or reap it manually.
593All other processes are not direct children, and will be cleaned up by
594AnyEvent::Fork itself.
595 682
596=cut 683=cut
597 684
598sub pid { 685sub pid {
599 $_[0][PID] 686 $_[0][PID]
730 817
731Even if not used otherwise, the socket can be a good indicator for the 818Even if not used otherwise, the socket can be a good indicator for the
732existence of the process - if the other process exits, you get a readable 819existence of the process - if the other process exits, you get a readable
733event on it, because exiting the process closes the socket (if it didn't 820event on it, because exiting the process closes the socket (if it didn't
734create any children using fork). 821create any children using fork).
822
823=over 4
824
825=item Compatibility to L<AnyEvent::Fork::Remote>
826
827If you want to write code that works with both this module and
828L<AnyEvent::Fork::Remote>, you need to write your code so that it assumes
829there are two file handles for communications, which might not be unix
830domain sockets. The C<run> function should start like this:
831
832 sub run {
833 my ($rfh, @args) = @_; # @args is your normal arguments
834 my $wfh = fileno $rfh ? $rfh : *STDOUT;
835
836 # now use $rfh for reading and $wfh for writing
837 }
838
839This checks whether the passed file handle is, in fact, the process
840C<STDIN> handle. If it is, then the function was invoked visa
841L<AnyEvent::Fork::Remote>, so STDIN should be used for reading and
842C<STDOUT> should be used for writing.
843
844In all other cases, the function was called via this module, and there is
845only one file handle that should be sued for reading and writing.
846
847=back
735 848
736Example: create a template for a process pool, pass a few strings, some 849Example: create a template for a process pool, pass a few strings, some
737file handles, then fork, pass one more string, and run some code. 850file handles, then fork, pass one more string, and run some code.
738 851
739 my $pool = AnyEvent::Fork 852 my $pool = AnyEvent::Fork
773 $self->_cmd (r => $func); 886 $self->_cmd (r => $func);
774} 887}
775 888
776=back 889=back
777 890
891=head2 EXPERIMENTAL METHODS
892
893These methods might go away completely or change behaviour, at any time.
894
895=over 4
896
897=item $proc->to_fh ($cb->($fh)) # EXPERIMENTAL, MIGHT BE REMOVED
898
899Flushes all commands out to the process and then calls the callback with
900the communications socket.
901
902The process object becomes unusable on return from this function - any
903further method calls result in undefined behaviour.
904
905The point of this method is to give you a file handle that you can pass
906to another process. In that other process, you can call C<new_from_fh
907AnyEvent::Fork $fh> to create a new C<AnyEvent::Fork> object from it,
908thereby effectively passing a fork object to another process.
909
910=cut
911
912sub to_fh {
913 my ($self, $cb) = @_;
914
915 $self->[CB] = $cb;
916
917 unless ($self->[WW]) {
918 $self->[CB]->($self->[FH]);
919 @$self = ();
920 }
921}
922
923=item new_from_fh AnyEvent::Fork $fh # EXPERIMENTAL, MIGHT BE REMOVED
924
925Takes a file handle originally rceeived by the C<to_fh> method and creates
926a new C<AnyEvent:Fork> object. The child process itself will not change in
927any way, i.e. it will keep all the modifications done to it before calling
928C<to_fh>.
929
930The new object is very much like the original object, except that the
931C<pid> method will return C<undef> even if the process is a direct child.
932
933=cut
934
935sub new_from_fh {
936 my ($class, $fh) = @_;
937
938 $class->_new ($fh)
939}
940
941=back
942
778=head1 PERFORMANCE 943=head1 PERFORMANCE
779 944
780Now for some unscientific benchmark numbers (all done on an amd64 945Now for some unscientific benchmark numbers (all done on an amd64
781GNU/Linux box). These are intended to give you an idea of the relative 946GNU/Linux box). These are intended to give you an idea of the relative
782performance you can expect, they are not meant to be absolute performance 947performance you can expect, they are not meant to be absolute performance
788 953
789 2079 new processes per second, using manual socketpair + fork 954 2079 new processes per second, using manual socketpair + fork
790 955
791Then I did the same thing, but instead of calling fork, I called 956Then I did the same thing, but instead of calling fork, I called
792AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the 957AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the
793socket form the child to close on exit. This does the same thing as manual 958socket from the child to close on exit. This does the same thing as manual
794socket pair + fork, except that what is forked is the template process 959socket pair + fork, except that what is forked is the template process
795(2440kB), and the socket needs to be passed to the server at the other end 960(2440kB), and the socket needs to be passed to the server at the other end
796of the socket first. 961of the socket first.
797 962
798 2307 new processes per second, using AnyEvent::Fork->new 963 2307 new processes per second, using AnyEvent::Fork->new
905to make it so, mostly due to the bloody broken perl that nobody seems to 1070to make it so, mostly due to the bloody broken perl that nobody seems to
906care about. The fork emulation is a bad joke - I have yet to see something 1071care about. The fork emulation is a bad joke - I have yet to see something
907useful that you can do with it without running into memory corruption 1072useful that you can do with it without running into memory corruption
908issues or other braindamage. Hrrrr. 1073issues or other braindamage. Hrrrr.
909 1074
1075Since fork is endlessly broken on win32 perls (it doesn't even remotely
1076work within it's documented limits) and quite obviously it's not getting
1077improved any time soon, the best way to proceed on windows would be to
1078always use C<new_exec> and thus never rely on perl's fork "emulation".
1079
910Cygwin perl is not supported at the moment due to some hilarious 1080Cygwin perl is not supported at the moment due to some hilarious
911shortcomings of its API - see L<IO::FDPoll> for more details. 1081shortcomings of its API - see L<IO::FDPoll> for more details. If you never
1082use C<send_fh> and always use C<new_exec> to create processes, it should
1083work though.
912 1084
913=head1 SEE ALSO 1085=head1 SEE ALSO
914 1086
915L<AnyEvent::Fork::Early>, to avoid executing a perl interpreter at all 1087L<AnyEvent::Fork::Early>, to avoid executing a perl interpreter at all
916(part of this distribution). 1088(part of this distribution).
917 1089
918L<AnyEvent::Fork::Template>, to create a process by forking the main 1090L<AnyEvent::Fork::Template>, to create a process by forking the main
919program at a convenient time (part of this distribution). 1091program at a convenient time (part of this distribution).
920 1092
1093L<AnyEvent::Fork::Remote>, for another way to create processes that is
1094mostly compatible to this module and modules building on top of it, but
1095works better with remote processes.
1096
921L<AnyEvent::Fork::RPC>, for simple RPC to child processes (on CPAN). 1097L<AnyEvent::Fork::RPC>, for simple RPC to child processes (on CPAN).
1098
1099L<AnyEvent::Fork::Pool>, for simple worker process pool (on CPAN).
922 1100
923=head1 AUTHOR AND CONTACT INFORMATION 1101=head1 AUTHOR AND CONTACT INFORMATION
924 1102
925 Marc Lehmann <schmorp@schmorp.de> 1103 Marc Lehmann <schmorp@schmorp.de>
926 http://software.schmorp.de/pkg/AnyEvent-Fork 1104 http://software.schmorp.de/pkg/AnyEvent-Fork

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines