… | |
… | |
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. |
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, |
|
|
43 | and so on. |
|
|
44 | |
42 | |
|
|
43 | Or you can implement it yourself in whatever way you like, use some |
|
|
44 | message-passing module such as L<AnyEvent::MP>, some pipe such as |
|
|
45 | L<AnyEvent::ZeroMQ>, use L<AnyEvent::Handle> on both sides to send |
|
|
46 | e.g. JSON or Storable messages, and so on. |
|
|
47 | |
|
|
48 | =head2 COMPARISON TO OTHER MODULES |
|
|
49 | |
|
|
50 | There is an abundance of modules on CPAN that do "something fork", such as |
|
|
51 | L<Parallel::ForkManager>, L<AnyEvent::ForkManager>, L<AnyEvent::Worker> |
|
|
52 | or L<AnyEvent::Subprocess>. There are modules that implement their own |
|
|
53 | process management, such as L<AnyEvent::DBI>. |
|
|
54 | |
|
|
55 | The problems that all these modules try to solve are real, however, none |
|
|
56 | of them (from what I have seen) tackle the very real problems of unwanted |
|
|
57 | memory sharing, efficiency, not being able to use event processing or |
|
|
58 | similar modules in the processes they create. |
|
|
59 | |
|
|
60 | This module doesn't try to replace any of them - instead it tries to solve |
|
|
61 | the problem of creating processes with a minimum of fuss and overhead (and |
|
|
62 | also luxury). Ideally, most of these would use AnyEvent::Fork internally, |
|
|
63 | except they were written before AnyEvent:Fork was available, so obviously |
|
|
64 | had to roll their own. |
|
|
65 | |
45 | =head1 PROBLEM STATEMENT |
66 | =head2 PROBLEM STATEMENT |
46 | |
67 | |
47 | There are two traditional ways to implement parallel processing on UNIX |
68 | There are two traditional ways to implement parallel processing on UNIX |
48 | like operating systems - fork and process, and fork+exec and process. They |
69 | like operating systems - fork and process, and fork+exec and process. They |
49 | have different advantages and disadvantages that I describe below, |
70 | have different advantages and disadvantages that I describe below, |
50 | together with how this module tries to mitigate the disadvantages. |
71 | together with how this module tries to mitigate the disadvantages. |
… | |
… | |
152 | |
173 | |
153 | # now $master_filehandle is connected to the |
174 | # now $master_filehandle is connected to the |
154 | # $slave_filehandle in the new process. |
175 | # $slave_filehandle in the new process. |
155 | }); |
176 | }); |
156 | |
177 | |
157 | MyModule::worker might look like this: |
178 | C<MyModule> might look like this: |
158 | |
179 | |
|
|
180 | package MyModule; |
|
|
181 | |
159 | sub MyModule::worker { |
182 | sub worker { |
160 | my ($slave_filehandle) = @_; |
183 | my ($slave_filehandle) = @_; |
161 | |
184 | |
162 | # now $slave_filehandle is connected to the $master_filehandle |
185 | # now $slave_filehandle is connected to the $master_filehandle |
163 | # in the original prorcess. have fun! |
186 | # in the original prorcess. have fun! |
164 | } |
187 | } |
… | |
… | |
183 | } |
206 | } |
184 | |
207 | |
185 | # now do other things - maybe use the filehandle provided by run |
208 | # now do other things - maybe use the filehandle provided by run |
186 | # to wait for the processes to die. or whatever. |
209 | # to wait for the processes to die. or whatever. |
187 | |
210 | |
188 | My::Server::run might look like this: |
211 | C<My::Server> might look like this: |
189 | |
212 | |
190 | sub My::Server::run { |
213 | package My::Server; |
|
|
214 | |
|
|
215 | sub run { |
191 | my ($slave, $listener, $id) = @_; |
216 | my ($slave, $listener, $id) = @_; |
192 | |
217 | |
193 | close $slave; # we do not use the socket, so close it to save resources |
218 | close $slave; # we do not use the socket, so close it to save resources |
194 | |
219 | |
195 | # we could go ballistic and use e.g. AnyEvent here, or IO::AIO, |
220 | # we could go ballistic and use e.g. AnyEvent here, or IO::AIO, |
… | |
… | |
199 | } |
224 | } |
200 | } |
225 | } |
201 | |
226 | |
202 | =head2 use AnyEvent::Fork as a faster fork+exec |
227 | =head2 use AnyEvent::Fork as a faster fork+exec |
203 | |
228 | |
204 | This runs /bin/echo hi, with stdout redirected to /tmp/log and stderr to |
229 | This runs C</bin/echo hi>, with standard output redirected to F</tmp/log> |
205 | the communications socket. It is usually faster than fork+exec, but still |
230 | and standard error redirected to the communications socket. It is usually |
206 | let's you prepare the environment. |
231 | faster than fork+exec, but still lets you prepare the environment. |
207 | |
232 | |
208 | open my $output, ">/tmp/log" or die "$!"; |
233 | open my $output, ">/tmp/log" or die "$!"; |
209 | |
234 | |
210 | AnyEvent::Fork |
235 | AnyEvent::Fork |
211 | ->new |
236 | ->new |
212 | ->eval (' |
237 | ->eval (' |
|
|
238 | # compile a helper function for later use |
213 | sub run { |
239 | sub run { |
214 | my ($fh, $output, @cmd) = @_; |
240 | my ($fh, $output, @cmd) = @_; |
215 | |
241 | |
216 | # perl will clear close-on-exec on STDOUT/STDERR |
242 | # perl will clear close-on-exec on STDOUT/STDERR |
217 | open STDOUT, ">&", $output or die; |
243 | open STDOUT, ">&", $output or die; |
… | |
… | |
228 | |
254 | |
229 | =head1 CONCEPTS |
255 | =head1 CONCEPTS |
230 | |
256 | |
231 | This module can create new processes either by executing a new perl |
257 | This module can create new processes either by executing a new perl |
232 | process, or by forking from an existing "template" process. |
258 | process, or by forking from an existing "template" process. |
|
|
259 | |
|
|
260 | All these processes are called "child processes" (whether they are direct |
|
|
261 | children or not), while the process that manages them is called the |
|
|
262 | "parent process". |
233 | |
263 | |
234 | Each such process comes with its own file handle that can be used to |
264 | Each such process comes with its own file handle that can be used to |
235 | communicate with it (it's actually a socket - one end in the new process, |
265 | communicate with it (it's actually a socket - one end in the new process, |
236 | one end in the main process), and among the things you can do in it are |
266 | one end in the main process), and among the things you can do in it are |
237 | load modules, fork new processes, send file handles to it, and execute |
267 | load modules, fork new processes, send file handles to it, and execute |
… | |
… | |
347 | use AnyEvent; |
377 | use AnyEvent; |
348 | use AnyEvent::Util (); |
378 | use AnyEvent::Util (); |
349 | |
379 | |
350 | use IO::FDPass; |
380 | use IO::FDPass; |
351 | |
381 | |
352 | our $VERSION = 0.5; |
382 | our $VERSION = 0.7; |
353 | |
|
|
354 | our $PERL; # the path to the perl interpreter, deduces with various forms of magic |
|
|
355 | |
|
|
356 | =over 4 |
|
|
357 | |
|
|
358 | =back |
|
|
359 | |
|
|
360 | =cut |
|
|
361 | |
383 | |
362 | # the early fork template process |
384 | # the early fork template process |
363 | our $EARLY; |
385 | our $EARLY; |
364 | |
386 | |
365 | # the empty template process |
387 | # the empty template process |
366 | our $TEMPLATE; |
388 | our $TEMPLATE; |
|
|
389 | |
|
|
390 | sub QUEUE() { 0 } |
|
|
391 | sub FH() { 1 } |
|
|
392 | sub WW() { 2 } |
|
|
393 | sub PID() { 3 } |
|
|
394 | sub CB() { 4 } |
|
|
395 | |
|
|
396 | sub _new { |
|
|
397 | my ($self, $fh, $pid) = @_; |
|
|
398 | |
|
|
399 | AnyEvent::Util::fh_nonblocking $fh, 1; |
|
|
400 | |
|
|
401 | $self = bless [ |
|
|
402 | [], # write queue - strings or fd's |
|
|
403 | $fh, |
|
|
404 | undef, # AE watcher |
|
|
405 | $pid, |
|
|
406 | ], $self; |
|
|
407 | |
|
|
408 | $self |
|
|
409 | } |
367 | |
410 | |
368 | sub _cmd { |
411 | sub _cmd { |
369 | my $self = shift; |
412 | my $self = shift; |
370 | |
413 | |
371 | # ideally, we would want to use "a (w/a)*" as format string, but perl |
414 | # ideally, we would want to use "a (w/a)*" as format string, but perl |
372 | # versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack |
415 | # versions from at least 5.8.9 to 5.16.3 are all buggy and can't unpack |
373 | # it. |
416 | # it. |
374 | push @{ $self->[2] }, pack "a L/a*", $_[0], $_[1]; |
417 | push @{ $self->[QUEUE] }, pack "a L/a*", $_[0], $_[1]; |
375 | |
418 | |
376 | $self->[3] ||= AE::io $self->[1], 1, sub { |
419 | $self->[WW] ||= AE::io $self->[FH], 1, sub { |
377 | do { |
420 | do { |
378 | # send the next "thing" in the queue - either a reference to an fh, |
421 | # send the next "thing" in the queue - either a reference to an fh, |
379 | # or a plain string. |
422 | # or a plain string. |
380 | |
423 | |
381 | if (ref $self->[2][0]) { |
424 | if (ref $self->[QUEUE][0]) { |
382 | # send fh |
425 | # send fh |
383 | unless (IO::FDPass::send fileno $self->[1], fileno ${ $self->[2][0] }) { |
426 | unless (IO::FDPass::send fileno $self->[FH], fileno ${ $self->[QUEUE][0] }) { |
384 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
427 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
385 | undef $self->[3]; |
428 | undef $self->[WW]; |
386 | die "AnyEvent::Fork: file descriptor send failure: $!"; |
429 | die "AnyEvent::Fork: file descriptor send failure: $!"; |
387 | } |
430 | } |
388 | |
431 | |
389 | shift @{ $self->[2] }; |
432 | shift @{ $self->[QUEUE] }; |
390 | |
433 | |
391 | } else { |
434 | } else { |
392 | # send string |
435 | # send string |
393 | my $len = syswrite $self->[1], $self->[2][0]; |
436 | my $len = syswrite $self->[FH], $self->[QUEUE][0]; |
394 | |
437 | |
395 | unless ($len) { |
438 | unless ($len) { |
396 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
439 | return if $! == Errno::EAGAIN || $! == Errno::EWOULDBLOCK; |
397 | undef $self->[3]; |
440 | undef $self->[3]; |
398 | die "AnyEvent::Fork: command write failure: $!"; |
441 | die "AnyEvent::Fork: command write failure: $!"; |
399 | } |
442 | } |
400 | |
443 | |
401 | substr $self->[2][0], 0, $len, ""; |
444 | substr $self->[QUEUE][0], 0, $len, ""; |
402 | shift @{ $self->[2] } unless length $self->[2][0]; |
445 | shift @{ $self->[QUEUE] } unless length $self->[QUEUE][0]; |
403 | } |
446 | } |
404 | } while @{ $self->[2] }; |
447 | } while @{ $self->[QUEUE] }; |
405 | |
448 | |
406 | # everything written |
449 | # everything written |
407 | undef $self->[3]; |
450 | undef $self->[WW]; |
408 | |
451 | |
409 | # invoke run callback, if any |
452 | # invoke run callback, if any |
410 | $self->[4]->($self->[1]) if $self->[4]; |
453 | $self->[CB]->($self->[FH]) if $self->[CB]; |
411 | }; |
454 | }; |
412 | |
455 | |
413 | () # make sure we don't leak the watcher |
456 | () # make sure we don't leak the watcher |
414 | } |
|
|
415 | |
|
|
416 | sub _new { |
|
|
417 | my ($self, $fh, $pid) = @_; |
|
|
418 | |
|
|
419 | AnyEvent::Util::fh_nonblocking $fh, 1; |
|
|
420 | |
|
|
421 | $self = bless [ |
|
|
422 | $pid, |
|
|
423 | $fh, |
|
|
424 | [], # write queue - strings or fd's |
|
|
425 | undef, # AE watcher |
|
|
426 | ], $self; |
|
|
427 | |
|
|
428 | $self |
|
|
429 | } |
457 | } |
430 | |
458 | |
431 | # fork template from current process, used by AnyEvent::Fork::Early/Template |
459 | # fork template from current process, used by AnyEvent::Fork::Early/Template |
432 | sub _new_fork { |
460 | sub _new_fork { |
433 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
461 | my ($fh, $slave) = AnyEvent::Util::portable_socketpair; |
… | |
… | |
438 | if ($pid eq 0) { |
466 | if ($pid eq 0) { |
439 | require AnyEvent::Fork::Serve; |
467 | require AnyEvent::Fork::Serve; |
440 | $AnyEvent::Fork::Serve::OWNER = $parent; |
468 | $AnyEvent::Fork::Serve::OWNER = $parent; |
441 | close $fh; |
469 | close $fh; |
442 | $0 = "$_[1] of $parent"; |
470 | $0 = "$_[1] of $parent"; |
443 | $SIG{CHLD} = 'IGNORE'; |
|
|
444 | AnyEvent::Fork::Serve::serve ($slave); |
471 | AnyEvent::Fork::Serve::serve ($slave); |
445 | exit 0; |
472 | exit 0; |
446 | } elsif (!$pid) { |
473 | } elsif (!$pid) { |
447 | die "AnyEvent::Fork::Early/Template: unable to fork template process: $!"; |
474 | die "AnyEvent::Fork::Early/Template: unable to fork template process: $!"; |
448 | } |
475 | } |
… | |
… | |
555 | } |
582 | } |
556 | |
583 | |
557 | =item $pid = $proc->pid |
584 | =item $pid = $proc->pid |
558 | |
585 | |
559 | Returns the process id of the process I<iff it is a direct child of the |
586 | Returns the process id of the process I<iff it is a direct child of the |
560 | process> running AnyEvent::Fork, and C<undef> otherwise. |
587 | process running AnyEvent::Fork>, and C<undef> otherwise. |
561 | |
588 | |
562 | Normally, only processes created via C<< AnyEvent::Fork->new_exec >> and |
589 | Normally, only processes created via C<< AnyEvent::Fork->new_exec >> and |
563 | L<AnyEvent::Fork::Template> are direct children, and you are responsible |
590 | L<AnyEvent::Fork::Template> are direct children, and you are responsible |
564 | to clean up their zombies when they die. |
591 | to clean up their zombies when they die. |
565 | |
592 | |
… | |
… | |
567 | AnyEvent::Fork itself. |
594 | AnyEvent::Fork itself. |
568 | |
595 | |
569 | =cut |
596 | =cut |
570 | |
597 | |
571 | sub pid { |
598 | sub pid { |
572 | $_[0][0] |
599 | $_[0][PID] |
573 | } |
600 | } |
574 | |
601 | |
575 | =item $proc = $proc->eval ($perlcode, @args) |
602 | =item $proc = $proc->eval ($perlcode, @args) |
576 | |
603 | |
577 | Evaluates the given C<$perlcode> as ... perl code, while setting C<@_> to |
604 | Evaluates the given C<$perlcode> as ... Perl code, while setting C<@_> to |
578 | the strings specified by C<@args>, in the "main" package. |
605 | the strings specified by C<@args>, in the "main" package. |
579 | |
606 | |
580 | This call is meant to do any custom initialisation that might be required |
607 | This call is meant to do any custom initialisation that might be required |
581 | (for example, the C<require> method uses it). It's not supposed to be used |
608 | (for example, the C<require> method uses it). It's not supposed to be used |
582 | to completely take over the process, use C<run> for that. |
609 | to completely take over the process, use C<run> for that. |
583 | |
610 | |
584 | The code will usually be executed after this call returns, and there is no |
611 | The code will usually be executed after this call returns, and there is no |
585 | way to pass anything back to the calling process. Any evaluation errors |
612 | way to pass anything back to the calling process. Any evaluation errors |
586 | will be reported to stderr and cause the process to exit. |
613 | will be reported to stderr and cause the process to exit. |
587 | |
614 | |
588 | If you want to execute some code to take over the process (see the |
615 | If you want to execute some code (that isn't in a module) to take over the |
589 | "fork+exec" example in the SYNOPSIS), you should compile a function via |
616 | process, you should compile a function via C<eval> first, and then call |
590 | C<eval> first, and then call it via C<run>. This also gives you access to |
617 | it via C<run>. This also gives you access to any arguments passed via the |
591 | any arguments passed via the C<send_xxx> methods, such as file handles. |
618 | C<send_xxx> methods, such as file handles. See the L<use AnyEvent::Fork as |
|
|
619 | a faster fork+exec> example to see it in action. |
592 | |
620 | |
593 | Returns the process object for easy chaining of method calls. |
621 | Returns the process object for easy chaining of method calls. |
594 | |
622 | |
595 | =cut |
623 | =cut |
596 | |
624 | |
… | |
… | |
622 | =item $proc = $proc->send_fh ($handle, ...) |
650 | =item $proc = $proc->send_fh ($handle, ...) |
623 | |
651 | |
624 | Send one or more file handles (I<not> file descriptors) to the process, |
652 | Send one or more file handles (I<not> file descriptors) to the process, |
625 | to prepare a call to C<run>. |
653 | to prepare a call to C<run>. |
626 | |
654 | |
627 | The process object keeps a reference to the handles until this is done, |
655 | The process object keeps a reference to the handles until they have |
628 | so you must not explicitly close the handles. This is most easily |
656 | been passed over to the process, so you must not explicitly close the |
629 | accomplished by simply not storing the file handles anywhere after passing |
657 | handles. This is most easily accomplished by simply not storing the file |
630 | them to this method. |
658 | handles anywhere after passing them to this method - when AnyEvent::Fork |
|
|
659 | is finished using them, perl will automatically close them. |
631 | |
660 | |
632 | Returns the process object for easy chaining of method calls. |
661 | Returns the process object for easy chaining of method calls. |
633 | |
662 | |
634 | Example: pass a file handle to a process, and release it without |
663 | Example: pass a file handle to a process, and release it without |
635 | closing. It will be closed automatically when it is no longer used. |
664 | closing. It will be closed automatically when it is no longer used. |
… | |
… | |
642 | sub send_fh { |
671 | sub send_fh { |
643 | my ($self, @fh) = @_; |
672 | my ($self, @fh) = @_; |
644 | |
673 | |
645 | for my $fh (@fh) { |
674 | for my $fh (@fh) { |
646 | $self->_cmd ("h"); |
675 | $self->_cmd ("h"); |
647 | push @{ $self->[2] }, \$fh; |
676 | push @{ $self->[QUEUE] }, \$fh; |
648 | } |
677 | } |
649 | |
678 | |
650 | $self |
679 | $self |
651 | } |
680 | } |
652 | |
681 | |
653 | =item $proc = $proc->send_arg ($string, ...) |
682 | =item $proc = $proc->send_arg ($string, ...) |
654 | |
683 | |
655 | Send one or more argument strings to the process, to prepare a call to |
684 | Send one or more argument strings to the process, to prepare a call to |
656 | C<run>. The strings can be any octet string. |
685 | C<run>. The strings can be any octet strings. |
657 | |
686 | |
658 | The protocol is optimised to pass a moderate number of relatively short |
687 | The protocol is optimised to pass a moderate number of relatively short |
659 | strings - while you can pass up to 4GB of data in one go, this is more |
688 | strings - while you can pass up to 4GB of data in one go, this is more |
660 | meant to pass some ID information or other startup info, not big chunks of |
689 | meant to pass some ID information or other startup info, not big chunks of |
661 | data. |
690 | data. |
… | |
… | |
677 | Enter the function specified by the function name in C<$func> in the |
706 | Enter the function specified by the function name in C<$func> in the |
678 | process. The function is called with the communication socket as first |
707 | process. The function is called with the communication socket as first |
679 | argument, followed by all file handles and string arguments sent earlier |
708 | argument, followed by all file handles and string arguments sent earlier |
680 | via C<send_fh> and C<send_arg> methods, in the order they were called. |
709 | via C<send_fh> and C<send_arg> methods, in the order they were called. |
681 | |
710 | |
|
|
711 | The process object becomes unusable on return from this function - any |
|
|
712 | further method calls result in undefined behaviour. |
|
|
713 | |
682 | The function name should be fully qualified, but if it isn't, it will be |
714 | The function name should be fully qualified, but if it isn't, it will be |
683 | looked up in the main package. |
715 | looked up in the C<main> package. |
684 | |
716 | |
685 | If the called function returns, doesn't exist, or any error occurs, the |
717 | If the called function returns, doesn't exist, or any error occurs, the |
686 | process exits. |
718 | process exits. |
687 | |
719 | |
688 | Preparing the process is done in the background - when all commands have |
720 | Preparing the process is done in the background - when all commands have |
689 | been sent, the callback is invoked with the local communications socket |
721 | been sent, the callback is invoked with the local communications socket |
690 | as argument. At this point you can start using the socket in any way you |
722 | as argument. At this point you can start using the socket in any way you |
691 | like. |
723 | like. |
692 | |
|
|
693 | The process object becomes unusable on return from this function - any |
|
|
694 | further method calls result in undefined behaviour. |
|
|
695 | |
724 | |
696 | If the communication socket isn't used, it should be closed on both sides, |
725 | If the communication socket isn't used, it should be closed on both sides, |
697 | to save on kernel memory. |
726 | to save on kernel memory. |
698 | |
727 | |
699 | The socket is non-blocking in the parent, and blocking in the newly |
728 | The socket is non-blocking in the parent, and blocking in the newly |
… | |
… | |
738 | =cut |
767 | =cut |
739 | |
768 | |
740 | sub run { |
769 | sub run { |
741 | my ($self, $func, $cb) = @_; |
770 | my ($self, $func, $cb) = @_; |
742 | |
771 | |
743 | $self->[4] = $cb; |
772 | $self->[CB] = $cb; |
744 | $self->_cmd (r => $func); |
773 | $self->_cmd (r => $func); |
745 | } |
774 | } |
746 | |
775 | |
747 | =back |
776 | =back |
748 | |
777 | |
… | |
… | |
774 | 479 vfork+execs per second, using AnyEvent::Fork->new_exec |
803 | 479 vfork+execs per second, using AnyEvent::Fork->new_exec |
775 | |
804 | |
776 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
805 | So how can C<< AnyEvent->new >> be faster than a standard fork, even |
777 | though it uses the same operations, but adds a lot of overhead? |
806 | though it uses the same operations, but adds a lot of overhead? |
778 | |
807 | |
779 | The difference is simply the process size: forking the 6MB process takes |
808 | The difference is simply the process size: forking the 5MB process takes |
780 | so much longer than forking the 2.5MB template process that the overhead |
809 | so much longer than forking the 2.5MB template process that the extra |
781 | introduced is canceled out. |
810 | overhead is canceled out. |
782 | |
811 | |
783 | If the benchmark process grows, the normal fork becomes even slower: |
812 | If the benchmark process grows, the normal fork becomes even slower: |
784 | |
813 | |
785 | 1340 new processes, manual fork in a 20MB process |
814 | 1340 new processes, manual fork of a 20MB process |
786 | 731 new processes, manual fork in a 200MB process |
815 | 731 new processes, manual fork of a 200MB process |
787 | 235 new processes, manual fork in a 2000MB process |
816 | 235 new processes, manual fork of a 2000MB process |
788 | |
817 | |
789 | What that means (to me) is that I can use this module without having a |
818 | What that means (to me) is that I can use this module without having a bad |
790 | very bad conscience because of the extra overhead required to start new |
819 | conscience because of the extra overhead required to start new processes. |
791 | processes. |
|
|
792 | |
820 | |
793 | =head1 TYPICAL PROBLEMS |
821 | =head1 TYPICAL PROBLEMS |
794 | |
822 | |
795 | This section lists typical problems that remain. I hope by recognising |
823 | This section lists typical problems that remain. I hope by recognising |
796 | them, most can be avoided. |
824 | them, most can be avoided. |
797 | |
825 | |
798 | =over 4 |
826 | =over 4 |
799 | |
827 | |
800 | =item "leaked" file descriptors for exec'ed processes |
828 | =item leaked file descriptors for exec'ed processes |
801 | |
829 | |
802 | POSIX systems inherit file descriptors by default when exec'ing a new |
830 | POSIX systems inherit file descriptors by default when exec'ing a new |
803 | process. While perl itself laudably sets the close-on-exec flags on new |
831 | process. While perl itself laudably sets the close-on-exec flags on new |
804 | file handles, most C libraries don't care, and even if all cared, it's |
832 | file handles, most C libraries don't care, and even if all cared, it's |
805 | often not possible to set the flag in a race-free manner. |
833 | often not possible to set the flag in a race-free manner. |
… | |
… | |
825 | libraries or the code that leaks those file descriptors. |
853 | libraries or the code that leaks those file descriptors. |
826 | |
854 | |
827 | Fortunately, most of these leaked descriptors do no harm, other than |
855 | Fortunately, most of these leaked descriptors do no harm, other than |
828 | sitting on some resources. |
856 | sitting on some resources. |
829 | |
857 | |
830 | =item "leaked" file descriptors for fork'ed processes |
858 | =item leaked file descriptors for fork'ed processes |
831 | |
859 | |
832 | Normally, L<AnyEvent::Fork> does start new processes by exec'ing them, |
860 | Normally, L<AnyEvent::Fork> does start new processes by exec'ing them, |
833 | which closes file descriptors not marked for being inherited. |
861 | which closes file descriptors not marked for being inherited. |
834 | |
862 | |
835 | However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer |
863 | However, L<AnyEvent::Fork::Early> and L<AnyEvent::Fork::Template> offer |
… | |
… | |
844 | |
872 | |
845 | The solution is to either not load these modules before use'ing |
873 | The solution is to either not load these modules before use'ing |
846 | L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay |
874 | L<AnyEvent::Fork::Early> or L<AnyEvent::Fork::Template>, or to delay |
847 | initialising them, for example, by calling C<init Gtk2> manually. |
875 | initialising them, for example, by calling C<init Gtk2> manually. |
848 | |
876 | |
849 | =item exit runs destructors |
877 | =item exiting calls object destructors |
850 | |
878 | |
851 | This only applies to users of Lc<AnyEvent::Fork:Early> and |
879 | This only applies to users of L<AnyEvent::Fork:Early> and |
852 | L<AnyEvent::Fork::Template>. |
880 | L<AnyEvent::Fork::Template>, or when initialising code creates objects |
|
|
881 | that reference external resources. |
853 | |
882 | |
854 | When a process created by AnyEvent::Fork exits, it might do so by calling |
883 | When a process created by AnyEvent::Fork exits, it might do so by calling |
855 | exit, or simply letting perl reach the end of the program. At which point |
884 | exit, or simply letting perl reach the end of the program. At which point |
856 | Perl runs all destructors. |
885 | Perl runs all destructors. |
857 | |
886 | |
… | |
… | |
876 | to make it so, mostly due to the bloody broken perl that nobody seems to |
905 | to make it so, mostly due to the bloody broken perl that nobody seems to |
877 | care about. The fork emulation is a bad joke - I have yet to see something |
906 | care about. The fork emulation is a bad joke - I have yet to see something |
878 | useful that you can do with it without running into memory corruption |
907 | useful that you can do with it without running into memory corruption |
879 | issues or other braindamage. Hrrrr. |
908 | issues or other braindamage. Hrrrr. |
880 | |
909 | |
881 | Cygwin perl is not supported at the moment, as it should implement fd |
910 | Cygwin perl is not supported at the moment due to some hilarious |
882 | passing, but doesn't, and rolling my own is hard, as cygwin doesn't |
911 | shortcomings of its API - see L<IO::FDPoll> for more details. |
883 | support enough functionality to do it. |
|
|
884 | |
912 | |
885 | =head1 SEE ALSO |
913 | =head1 SEE ALSO |
886 | |
914 | |
887 | L<AnyEvent::Fork::Early> (to avoid executing a perl interpreter), |
915 | L<AnyEvent::Fork::Early>, to avoid executing a perl interpreter at all |
|
|
916 | (part of this distribution). |
|
|
917 | |
888 | L<AnyEvent::Fork::Template> (to create a process by forking the main |
918 | L<AnyEvent::Fork::Template>, to create a process by forking the main |
889 | program at a convenient time). |
919 | program at a convenient time (part of this distribution). |
890 | |
920 | |
891 | =head1 AUTHOR |
921 | L<AnyEvent::Fork::RPC>, for simple RPC to child processes (on CPAN). |
|
|
922 | |
|
|
923 | =head1 AUTHOR AND CONTACT INFORMATION |
892 | |
924 | |
893 | Marc Lehmann <schmorp@schmorp.de> |
925 | Marc Lehmann <schmorp@schmorp.de> |
894 | http://home.schmorp.de/ |
926 | http://software.schmorp.de/pkg/AnyEvent-Fork |
895 | |
927 | |
896 | =cut |
928 | =cut |
897 | |
929 | |
898 | 1 |
930 | 1 |
899 | |
931 | |