… | |
… | |
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. |
38 | |
38 | |
39 | If you need some form of RPC, you can either implement it yourself |
39 | If you need some form of RPC, you could use the L<AnyEvent::Fork::RPC> |
40 | in whatever way you like, use some message-passing module such |
40 | companion module, which adds simple RPC/job queueing to a process created |
41 | as L<AnyEvent::MP>, some pipe such as L<AnyEvent::ZeroMQ>, use |
41 | by this module. |
42 | L<AnyEvent::Handle> on both sides to send e.g. JSON or Storable messages, |
42 | |
43 | and so on. |
43 | And if you need some automatic process pool management on top of |
|
|
44 | L<AnyEvent::Fork::RPC>, you can look at the L<AnyEvent::Fork::Pool> |
|
|
45 | companion module. |
|
|
46 | |
|
|
47 | Or you can implement it yourself in whatever way you like: use some |
|
|
48 | message-passing module such as L<AnyEvent::MP>, some pipe such as |
|
|
49 | L<AnyEvent::ZeroMQ>, use L<AnyEvent::Handle> on both sides to send |
|
|
50 | e.g. JSON or Storable messages, and so on. |
44 | |
51 | |
45 | =head2 COMPARISON TO OTHER MODULES |
52 | =head2 COMPARISON TO OTHER MODULES |
46 | |
53 | |
47 | There is an abundance of modules on CPAN that do "something fork", such as |
54 | There is an abundance of modules on CPAN that do "something fork", such as |
48 | L<Parallel::ForkManager>, L<AnyEvent::ForkManager>, L<AnyEvent::Worker> |
55 | L<Parallel::ForkManager>, L<AnyEvent::ForkManager>, L<AnyEvent::Worker> |
… | |
… | |
221 | } |
228 | } |
222 | } |
229 | } |
223 | |
230 | |
224 | =head2 use AnyEvent::Fork as a faster fork+exec |
231 | =head2 use AnyEvent::Fork as a faster fork+exec |
225 | |
232 | |
226 | This runs C</bin/echo hi>, with stdandard output redirected to /tmp/log |
233 | This runs C</bin/echo hi>, with standard output redirected to F</tmp/log> |
227 | and standard error redirected to the communications socket. It is usually |
234 | and standard error redirected to the communications socket. It is usually |
228 | faster than fork+exec, but still lets you prepare the environment. |
235 | faster than fork+exec, but still lets you prepare the environment. |
229 | |
236 | |
230 | open my $output, ">/tmp/log" or die "$!"; |
237 | open my $output, ">/tmp/log" or die "$!"; |
231 | |
238 | |
… | |
… | |
247 | ->send_arg ("/bin/echo", "hi") |
254 | ->send_arg ("/bin/echo", "hi") |
248 | ->run ("run", my $cv = AE::cv); |
255 | ->run ("run", my $cv = AE::cv); |
249 | |
256 | |
250 | my $stderr = $cv->recv; |
257 | my $stderr = $cv->recv; |
251 | |
258 | |
|
|
259 | =head2 For stingy users: put the worker code into a C<DATA> section. |
|
|
260 | |
|
|
261 | When you want to be stingy with files, you cna put your code into the |
|
|
262 | C<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 |
|
|
278 | all. |
|
|
279 | |
|
|
280 | For single-file scripts it can be inconvenient to rely on external |
|
|
281 | files - even when using < C<DATA> section, you still need to C<exec> |
|
|
282 | an external perl interpreter, which might not be available when using |
|
|
283 | L<App::Staticperl>, L<Urlader> or L<PAR::Packer> for example. |
|
|
284 | |
|
|
285 | Two modules help here - L<AnyEvent::Fork::Early> forks a template process |
|
|
286 | for all further calls to C<new_exec>, and L<AnyEvent::Fork::Template> |
|
|
287 | forks the main program as a template process. |
|
|
288 | |
|
|
289 | Here 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 | |
252 | =head1 CONCEPTS |
328 | =head1 CONCEPTS |
253 | |
329 | |
254 | This module can create new processes either by executing a new perl |
330 | This module can create new processes either by executing a new perl |
255 | process, or by forking from an existing "template" process. |
331 | process, or by forking from an existing "template" process. |
|
|
332 | |
|
|
333 | All these processes are called "child processes" (whether they are direct |
|
|
334 | children or not), while the process that manages them is called the |
|
|
335 | "parent process". |
256 | |
336 | |
257 | Each such process comes with its own file handle that can be used to |
337 | Each such process comes with its own file handle that can be used to |
258 | communicate with it (it's actually a socket - one end in the new process, |
338 | communicate with it (it's actually a socket - one end in the new process, |
259 | one end in the main process), and among the things you can do in it are |
339 | one end in the main process), and among the things you can do in it are |
260 | load modules, fork new processes, send file handles to it, and execute |
340 | load modules, fork new processes, send file handles to it, and execute |
… | |
… | |
370 | use AnyEvent; |
450 | use AnyEvent; |
371 | use AnyEvent::Util (); |
451 | use AnyEvent::Util (); |
372 | |
452 | |
373 | use IO::FDPass; |
453 | use IO::FDPass; |
374 | |
454 | |
375 | our $VERSION = 0.6; |
455 | our $VERSION = 1.1; |
376 | |
|
|
377 | =over 4 |
|
|
378 | |
|
|
379 | =back |
|
|
380 | |
|
|
381 | =cut |
|
|
382 | |
456 | |
383 | # the early fork template process |
457 | # the early fork template process |
384 | our $EARLY; |
458 | our $EARLY; |
385 | |
459 | |
386 | # the empty template process |
460 | # the empty template process |
387 | our $TEMPLATE; |
461 | our $TEMPLATE; |
|
|
462 | |
|
|
463 | sub QUEUE() { 0 } |
|
|
464 | sub FH() { 1 } |
|
|
465 | sub WW() { 2 } |
|
|
466 | sub PID() { 3 } |
|
|
467 | sub CB() { 4 } |
|
|
468 | |
|
|
469 | sub _new { |
|
|
470 | my ($self, $fh, $pid) = @_; |
|
|
471 | |
|
|
472 | AnyEvent::Util::fh_nonblocking $fh, 1; |
|
|
473 | |
|
|
474 | $self = bless [ |
|
|
475 | [], # write queue - strings or fd's |
|
|
476 | $fh, |
|
|
477 | undef, # AE watcher |
|
|
478 | $pid, |
|
|
479 | ], $self; |
|
|
480 | |
|
|
481 | $self |
|
|
482 | } |
388 | |
483 | |
389 | sub _cmd { |
484 | sub _cmd { |
390 | my $self = shift; |
485 | my $self = shift; |
391 | |
486 | |
392 | # ideally, we would want to use "a (w/a)*" as format string, but perl |
487 | # ideally, we would want to use "a (w/a)*" as format string, but perl |
393 | # versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack |
488 | # versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack |
394 | # it. |
489 | # it. |
395 | push @{ $self->[2] }, pack "a L/a*", $_[0], $_[1]; |
490 | push @{ $self->[QUEUE] }, pack "a L/a*", $_[0], $_[1]; |
396 | |
491 | |
397 | $self->[3] ||= AE::io $self->[1], 1, sub { |
492 | $self->[WW] ||= AE::io $self->[FH], 1, sub { |
398 | do { |
493 | do { |
399 | # send the next "thing" in the queue - either a reference to an fh, |
494 | # send the next "thing" in the queue - either a reference to an fh, |
400 | # or a plain string. |
495 | # or a plain string. |
401 | |
496 | |
402 | if (ref $self->[2][0]) { |
497 | if (ref $self->[QUEUE][0]) { |
403 | # send fh |
498 | # send fh |
404 | unless (IO::FDPass::send fileno $self->[1], fileno ${ $self->[2][0] }) { |
499 | unless (IO::FDPass::send fileno $self->[FH], fileno ${ $self->[QUEUE][0] }) { |
405 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
500 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
406 | undef $self->[3]; |
501 | undef $self->[WW]; |
407 | die "AnyEvent::Fork: file descriptor send failure: $!"; |
502 | die "AnyEvent::Fork: file descriptor send failure: $!"; |
408 | } |
503 | } |
409 | |
504 | |
410 | shift @{ $self->[2] }; |
505 | shift @{ $self->[QUEUE] }; |
411 | |
506 | |
412 | } else { |
507 | } else { |
413 | # send string |
508 | # send string |
414 | my $len = syswrite $self->[1], $self->[2][0]; |
509 | my $len = syswrite $self->[FH], $self->[QUEUE][0]; |
415 | |
510 | |
416 | unless ($len) { |
511 | unless ($len) { |
417 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
512 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
418 | undef $self->[3]; |
513 | undef $self->[WW]; |
419 | die "AnyEvent::Fork: command write failure: $!"; |
514 | die "AnyEvent::Fork: command write failure: $!"; |
420 | } |
515 | } |
421 | |
516 | |
422 | substr $self->[2][0], 0, $len, ""; |
517 | substr $self->[QUEUE][0], 0, $len, ""; |
423 | shift @{ $self->[2] } unless length $self->[2][0]; |
518 | shift @{ $self->[QUEUE] } unless length $self->[QUEUE][0]; |
424 | } |
519 | } |
425 | } while @{ $self->[2] }; |
520 | } while @{ $self->[QUEUE] }; |
426 | |
521 | |
427 | # everything written |
522 | # everything written |
428 | undef $self->[3]; |
523 | undef $self->[WW]; |
429 | |
524 | |
430 | # invoke run callback, if any |
525 | # invoke run callback, if any |
431 | $self->[4]->($self->[1]) if $self->[4]; |
526 | if ($self->[CB]) { |
|
|
527 | $self->[CB]->($self->[FH]); |
|
|
528 | @$self = (); |
|
|
529 | } |
432 | }; |
530 | }; |
433 | |
531 | |
434 | () # make sure we don't leak the watcher |
532 | () # make sure we don't leak the watcher |
435 | } |
|
|
436 | |
|
|
437 | sub _new { |
|
|
438 | my ($self, $fh, $pid) = @_; |
|
|
439 | |
|
|
440 | AnyEvent::Util::fh_nonblocking $fh, 1; |
|
|
441 | |
|
|
442 | $self = bless [ |
|
|
443 | $pid, |
|
|
444 | $fh, |
|
|
445 | [], # write queue - strings or fd's |
|
|
446 | undef, # AE watcher |
|
|
447 | ], $self; |
|
|
448 | |
|
|
449 | $self |
|
|
450 | } |
533 | } |
451 | |
534 | |
452 | # fork template from current process, used by AnyEvent::Fork::Early/Template |
535 | # fork template from current process, used by AnyEvent::Fork::Early/Template |
453 | sub _new_fork { |
536 | sub _new_fork { |
454 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
537 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
… | |
… | |
522 | |
605 | |
523 | You should use C<new> whenever possible, except when having a template |
606 | You should use C<new> whenever possible, except when having a template |
524 | process around is unacceptable. |
607 | process around is unacceptable. |
525 | |
608 | |
526 | The path to the perl interpreter is divined using various methods - first |
609 | The path to the perl interpreter is divined using various methods - first |
527 | C<$^X> is investigated to see if the path ends with something that sounds |
610 | C<$^X> is investigated to see if the path ends with something that looks |
528 | as if it were the perl interpreter. Failing this, the module falls back to |
611 | as if it were the perl interpreter. Failing this, the module falls back to |
529 | using C<$Config::Config{perlpath}>. |
612 | using C<$Config::Config{perlpath}>. |
530 | |
613 | |
|
|
614 | The path to perl can also be overriden by setting the global variable |
|
|
615 | C<$AnyEvent::Fork::PERL> - it's value will be used for all subsequent |
|
|
616 | invocations. |
|
|
617 | |
531 | =cut |
618 | =cut |
|
|
619 | |
|
|
620 | our $PERL; |
532 | |
621 | |
533 | sub new_exec { |
622 | sub new_exec { |
534 | my ($self) = @_; |
623 | my ($self) = @_; |
535 | |
624 | |
536 | return $EARLY->fork |
625 | return $EARLY->fork |
537 | if $EARLY; |
626 | if $EARLY; |
538 | |
627 | |
|
|
628 | unless (defined $PERL) { |
539 | # first find path of perl |
629 | # first find path of perl |
540 | my $perl = $; |
630 | my $perl = $; |
541 | |
631 | |
542 | # 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. |
543 | # 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 |
544 | unless ( |
634 | unless ( |
545 | ($^O eq "MSWin32" || $perl =~ m%^/%) |
635 | ($^O eq "MSWin32" || $perl =~ m%^/%) |
546 | && $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i |
636 | && $perl =~ m%[/\\]perl(?:[0-9]+(\.[0-9]+)+)?(\.exe)?$%i |
547 | ) { |
637 | ) { |
548 | # if it doesn't look perlish enough, try Config |
638 | # if it doesn't look perlish enough, try Config |
549 | require Config; |
639 | require Config; |
550 | $perl = $Config::Config{perlpath}; |
640 | $perl = $Config::Config{perlpath}; |
551 | $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; |
552 | } |
645 | } |
553 | |
646 | |
554 | require Proc::FastSpawn; |
647 | require Proc::FastSpawn; |
555 | |
648 | |
556 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
649 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
… | |
… | |
564 | #local $ENV{PERL5LIB} = join ":", grep !ref, @INC; |
657 | #local $ENV{PERL5LIB} = join ":", grep !ref, @INC; |
565 | my %env = %ENV; |
658 | my %env = %ENV; |
566 | $env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC; |
659 | $env{PERL5LIB} = join +($^O eq "MSWin32" ? ";" : ":"), grep !ref, @INC; |
567 | |
660 | |
568 | my $pid = Proc::FastSpawn::spawn ( |
661 | my $pid = Proc::FastSpawn::spawn ( |
569 | $perl, |
662 | $PERL, |
570 | ["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$], |
663 | ["perl", "-MAnyEvent::Fork::Serve", "-e", "AnyEvent::Fork::Serve::me", fileno $slave, $$], |
571 | [map "$_=$env{$_}", keys %env], |
664 | [map "$_=$env{$_}", keys %env], |
572 | ) or die "unable to spawn AnyEvent::Fork server: $!"; |
665 | ) or die "unable to spawn AnyEvent::Fork server: $!"; |
573 | |
666 | |
574 | $self->_new ($fh, $pid) |
667 | $self->_new ($fh, $pid) |
575 | } |
668 | } |
576 | |
669 | |
577 | =item $pid = $proc->pid |
670 | =item $pid = $proc->pid |
578 | |
671 | |
579 | Returns the process id of the process I<iff it is a direct child of the |
672 | Returns the process id of the process I<iff it is a direct child of the |
580 | process running AnyEvent::Fork>, and C<undef> otherwise. |
673 | process running AnyEvent::Fork>, and C<undef> otherwise. As a general |
|
|
674 | rule (that you cannot rely upon), processes created via C<new_exec>, |
|
|
675 | L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template> are direct |
|
|
676 | children, while all other processes are not. |
581 | |
677 | |
582 | Normally, only processes created via C<< AnyEvent::Fork->new_exec >> and |
678 | Or in other words, you do not normally have to take care of zombies for |
583 | L<AnyEvent::Fork::Template> are direct children, and you are responsible |
679 | processes created via C<new>, but when in doubt, or zombies are a problem, |
584 | to clean up their zombies when they die. |
680 | you need to check whether a process is a diretc child by calling this |
585 | |
681 | method, and possibly creating a child watcher or reap it manually. |
586 | All other processes are not direct children, and will be cleaned up by |
|
|
587 | AnyEvent::Fork itself. |
|
|
588 | |
682 | |
589 | =cut |
683 | =cut |
590 | |
684 | |
591 | sub pid { |
685 | sub pid { |
592 | $_[0][0] |
686 | $_[0][PID] |
593 | } |
687 | } |
594 | |
688 | |
595 | =item $proc = $proc->eval ($perlcode, @args) |
689 | =item $proc = $proc->eval ($perlcode, @args) |
596 | |
690 | |
597 | Evaluates the given C<$perlcode> as ... perl code, while setting C<@_> to |
691 | Evaluates the given C<$perlcode> as ... Perl code, while setting C<@_> to |
598 | the strings specified by C<@args>, in the "main" package. |
692 | the strings specified by C<@args>, in the "main" package. |
599 | |
693 | |
600 | This call is meant to do any custom initialisation that might be required |
694 | This call is meant to do any custom initialisation that might be required |
601 | (for example, the C<require> method uses it). It's not supposed to be used |
695 | (for example, the C<require> method uses it). It's not supposed to be used |
602 | to completely take over the process, use C<run> for that. |
696 | to completely take over the process, use C<run> for that. |
… | |
… | |
664 | sub send_fh { |
758 | sub send_fh { |
665 | my ($self, @fh) = @_; |
759 | my ($self, @fh) = @_; |
666 | |
760 | |
667 | for my $fh (@fh) { |
761 | for my $fh (@fh) { |
668 | $self->_cmd ("h"); |
762 | $self->_cmd ("h"); |
669 | push @{ $self->[2] }, \$fh; |
763 | push @{ $self->[QUEUE] }, \$fh; |
670 | } |
764 | } |
671 | |
765 | |
672 | $self |
766 | $self |
673 | } |
767 | } |
674 | |
768 | |
… | |
… | |
723 | |
817 | |
724 | Even if not used otherwise, the socket can be a good indicator for the |
818 | Even if not used otherwise, the socket can be a good indicator for the |
725 | existence of the process - if the other process exits, you get a readable |
819 | existence of the process - if the other process exits, you get a readable |
726 | event on it, because exiting the process closes the socket (if it didn't |
820 | event on it, because exiting the process closes the socket (if it didn't |
727 | create any children using fork). |
821 | create any children using fork). |
|
|
822 | |
|
|
823 | =over 4 |
|
|
824 | |
|
|
825 | =item Compatibility to L<AnyEvent::Fork::Remote> |
|
|
826 | |
|
|
827 | If you want to write code that works with both this module and |
|
|
828 | L<AnyEvent::Fork::Remote>, you need to write your code so that it assumes |
|
|
829 | there are two file handles for communications, which might not be unix |
|
|
830 | domain 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 | |
|
|
839 | This checks whether the passed file handle is, in fact, the process |
|
|
840 | C<STDIN> handle. If it is, then the function was invoked visa |
|
|
841 | L<AnyEvent::Fork::Remote>, so STDIN should be used for reading and |
|
|
842 | C<STDOUT> should be used for writing. |
|
|
843 | |
|
|
844 | In all other cases, the function was called via this module, and there is |
|
|
845 | only one file handle that should be sued for reading and writing. |
|
|
846 | |
|
|
847 | =back |
728 | |
848 | |
729 | Example: create a template for a process pool, pass a few strings, some |
849 | Example: create a template for a process pool, pass a few strings, some |
730 | file handles, then fork, pass one more string, and run some code. |
850 | file handles, then fork, pass one more string, and run some code. |
731 | |
851 | |
732 | my $pool = AnyEvent::Fork |
852 | my $pool = AnyEvent::Fork |
… | |
… | |
760 | =cut |
880 | =cut |
761 | |
881 | |
762 | sub run { |
882 | sub run { |
763 | my ($self, $func, $cb) = @_; |
883 | my ($self, $func, $cb) = @_; |
764 | |
884 | |
765 | $self->[4] = $cb; |
885 | $self->[CB] = $cb; |
766 | $self->_cmd (r => $func); |
886 | $self->_cmd (r => $func); |
|
|
887 | } |
|
|
888 | |
|
|
889 | =back |
|
|
890 | |
|
|
891 | =head2 EXPERIMENTAL METHODS |
|
|
892 | |
|
|
893 | These 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 | |
|
|
899 | Flushes all commands out to the process and then calls the callback with |
|
|
900 | the communications socket. |
|
|
901 | |
|
|
902 | The process object becomes unusable on return from this function - any |
|
|
903 | further method calls result in undefined behaviour. |
|
|
904 | |
|
|
905 | The point of this method is to give you a file handle that you can pass |
|
|
906 | to another process. In that other process, you can call C<new_from_fh |
|
|
907 | AnyEvent::Fork $fh> to create a new C<AnyEvent::Fork> object from it, |
|
|
908 | thereby effectively passing a fork object to another process. |
|
|
909 | |
|
|
910 | =cut |
|
|
911 | |
|
|
912 | sub 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 | |
|
|
925 | Takes a file handle originally rceeived by the C<to_fh> method and creates |
|
|
926 | a new C<AnyEvent:Fork> object. The child process itself will not change in |
|
|
927 | any way, i.e. it will keep all the modifications done to it before calling |
|
|
928 | C<to_fh>. |
|
|
929 | |
|
|
930 | The new object is very much like the original object, except that the |
|
|
931 | C<pid> method will return C<undef> even if the process is a direct child. |
|
|
932 | |
|
|
933 | =cut |
|
|
934 | |
|
|
935 | sub new_from_fh { |
|
|
936 | my ($class, $fh) = @_; |
|
|
937 | |
|
|
938 | $class->_new ($fh) |
767 | } |
939 | } |
768 | |
940 | |
769 | =back |
941 | =back |
770 | |
942 | |
771 | =head1 PERFORMANCE |
943 | =head1 PERFORMANCE |
… | |
… | |
781 | |
953 | |
782 | 2079 new processes per second, using manual socketpair + fork |
954 | 2079 new processes per second, using manual socketpair + fork |
783 | |
955 | |
784 | Then I did the same thing, but instead of calling fork, I called |
956 | Then I did the same thing, but instead of calling fork, I called |
785 | AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the |
957 | AnyEvent::Fork->new->run ("CORE::exit") and then again waited for the |
786 | socket form the child to close on exit. This does the same thing as manual |
958 | socket from the child to close on exit. This does the same thing as manual |
787 | socket pair + fork, except that what is forked is the template process |
959 | socket pair + fork, except that what is forked is the template process |
788 | (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 |
789 | of the socket first. |
961 | of the socket first. |
790 | |
962 | |
791 | 2307 new processes per second, using AnyEvent::Fork->new |
963 | 2307 new processes per second, using AnyEvent::Fork->new |
… | |
… | |
798 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
970 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
799 | though it uses the same operations, but adds a lot of overhead? |
971 | though it uses the same operations, but adds a lot of overhead? |
800 | |
972 | |
801 | The difference is simply the process size: forking the 5MB process takes |
973 | The difference is simply the process size: forking the 5MB process takes |
802 | so much longer than forking the 2.5MB template process that the extra |
974 | so much longer than forking the 2.5MB template process that the extra |
803 | overhead introduced is canceled out. |
975 | overhead is canceled out. |
804 | |
976 | |
805 | If the benchmark process grows, the normal fork becomes even slower: |
977 | If the benchmark process grows, the normal fork becomes even slower: |
806 | |
978 | |
807 | 1340 new processes, manual fork of a 20MB process |
979 | 1340 new processes, manual fork of a 20MB process |
808 | 731 new processes, manual fork of a 200MB process |
980 | 731 new processes, manual fork of a 200MB process |
… | |
… | |
868 | initialising them, for example, by calling C<init Gtk2> manually. |
1040 | initialising them, for example, by calling C<init Gtk2> manually. |
869 | |
1041 | |
870 | =item exiting calls object destructors |
1042 | =item exiting calls object destructors |
871 | |
1043 | |
872 | This only applies to users of L<AnyEvent::Fork:Early> and |
1044 | This only applies to users of L<AnyEvent::Fork:Early> and |
873 | L<AnyEvent::Fork::Template>, or when initialiasing code creates objects |
1045 | L<AnyEvent::Fork::Template>, or when initialising code creates objects |
874 | that reference external resources. |
1046 | that reference external resources. |
875 | |
1047 | |
876 | When a process created by AnyEvent::Fork exits, it might do so by calling |
1048 | When a process created by AnyEvent::Fork exits, it might do so by calling |
877 | exit, or simply letting perl reach the end of the program. At which point |
1049 | exit, or simply letting perl reach the end of the program. At which point |
878 | Perl runs all destructors. |
1050 | Perl runs all destructors. |
… | |
… | |
898 | to make it so, mostly due to the bloody broken perl that nobody seems to |
1070 | to make it so, mostly due to the bloody broken perl that nobody seems to |
899 | care about. The fork emulation is a bad joke - I have yet to see something |
1071 | care about. The fork emulation is a bad joke - I have yet to see something |
900 | useful that you can do with it without running into memory corruption |
1072 | useful that you can do with it without running into memory corruption |
901 | issues or other braindamage. Hrrrr. |
1073 | issues or other braindamage. Hrrrr. |
902 | |
1074 | |
|
|
1075 | Since fork is endlessly broken on win32 perls (it doesn't even remotely |
|
|
1076 | work within it's documented limits) and quite obviously it's not getting |
|
|
1077 | improved any time soon, the best way to proceed on windows would be to |
|
|
1078 | always use C<new_exec> and thus never rely on perl's fork "emulation". |
|
|
1079 | |
903 | Cygwin perl is not supported at the moment due to some hilarious |
1080 | Cygwin perl is not supported at the moment due to some hilarious |
904 | shortcomings of its API - see L<IO::FDPoll> for more details. |
1081 | shortcomings of its API - see L<IO::FDPoll> for more details. If you never |
|
|
1082 | use C<send_fh> and always use C<new_exec> to create processes, it should |
|
|
1083 | work though. |
905 | |
1084 | |
906 | =head1 SEE ALSO |
1085 | =head1 SEE ALSO |
907 | |
1086 | |
908 | L<AnyEvent::Fork::Early> (to avoid executing a perl interpreter), |
1087 | L<AnyEvent::Fork::Early>, to avoid executing a perl interpreter at all |
|
|
1088 | (part of this distribution). |
|
|
1089 | |
909 | L<AnyEvent::Fork::Template> (to create a process by forking the main |
1090 | L<AnyEvent::Fork::Template>, to create a process by forking the main |
910 | program at a convenient time). |
1091 | program at a convenient time (part of this distribution). |
911 | |
1092 | |
912 | =head1 AUTHOR |
1093 | L<AnyEvent::Fork::Remote>, for another way to create processes that is |
|
|
1094 | mostly compatible to this module and modules building on top of it, but |
|
|
1095 | works better with remote processes. |
|
|
1096 | |
|
|
1097 | L<AnyEvent::Fork::RPC>, for simple RPC to child processes (on CPAN). |
|
|
1098 | |
|
|
1099 | L<AnyEvent::Fork::Pool>, for simple worker process pool (on CPAN). |
|
|
1100 | |
|
|
1101 | =head1 AUTHOR AND CONTACT INFORMATION |
913 | |
1102 | |
914 | Marc Lehmann <schmorp@schmorp.de> |
1103 | Marc Lehmann <schmorp@schmorp.de> |
915 | http://home.schmorp.de/ |
1104 | http://software.schmorp.de/pkg/AnyEvent-Fork |
916 | |
1105 | |
917 | =cut |
1106 | =cut |
918 | |
1107 | |
919 | 1 |
1108 | 1 |
920 | |
1109 | |