[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.77 by root, Fri Apr 25 09:00:37 2008 UTC vs.
Revision 1.83 by root, Fri Apr 25 13:39:08 2008 UTC

 module.
 During the first call of any watcher-creation method, the module tries
 to detect the currently loaded event loop by probing whether one of the
 following modules is already loaded: L<Coro::EV>, L<Coro::Event>, L<EV>,
-L<Event>, L<Glib>, L<Tk>, L<AnyEvent::Impl::Perl>, L<Event::Lib>, L<Qt>,
+L<Event>, L<Glib>, L<AnyEvent::Impl::Perl>, L<Tk>, L<Event::Lib>, L<Qt>,
 L<POE>. The first one found is used. If none are found, the module tries
-to load these modules (excluding Event::Lib, Qt and POE as the pure perl
+to load these modules (excluding Tk, Event::Lib, Qt and POE as the pure perl
 adaptor should always succeed) in the order given. The first one that can
 be successfully loaded will be used. If, after this, still none could be
 found, AnyEvent will fall back to a pure-perl event loop, which is not
 very efficient, but should work everywhere.
 Note that C<my $w; $w => combination. This is necessary because in Perl,
 my variables are only visible after the statement in which they are
 declared.
-=head2 IO WATCHERS
+=head2 I/O WATCHERS
 You can create an I/O watcher by calling the C<< AnyEvent->io >> method
 with the following mandatory key-value pairs as arguments:
 C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for
 events. C<poll> must be a string that is either C<r> or C<w>, which
 creates a watcher waiting for "r"eadable or "w"ritable events,
 respectively. C<cb> is the callback to invoke each time the file handle
 becomes ready.
-As long as the I/O watcher exists it will keep the file descriptor or a
+The I/O watcher might use the underlying file descriptor or a copy of it.
-copy of it alive/open.
 It is not allowed to close a file handle as long as any watcher is active
 on the underlying file descriptor.
 Some event loops issue spurious readyness notifications, so you should
 always use non-blocking calls when reading/writing from/to your file
 watches for any child process exit). The watcher will trigger as often
 as status change for the child are received. This works by installing a
 signal handler for C<SIGCHLD>. The callback will be called with the pid
 and exit status (as returned by waitpid).
-Example: wait for pid 1333
+There is a slight catch to child watchers, however: you usually start them
+I<after> the child process was created, and this means the process could
+have exited already (and no SIGCHLD will be sent anymore).
+Not all event models handle this correctly (POE doesn't), but even for
+event models that I<do> handle this correctly, they usually need to be
+loaded before the process exits (i.e. before you fork in the first place).
+This means you cannot create a child watcher as the very first thing in an
+AnyEvent program, you I<have> to create at least one watcher before you
+C<fork> the child (alternatively, you can call C<AnyEvent::detect>).
+Example: fork a process and wait for it
+  my $done = AnyEvent->condvar;
+  AnyEvent::detect; # force event module to be initialised
+  my $pid = fork or exit 5;
   my $w = AnyEvent->child (
-     pid => 1333,
+     pid => $pid,
      cb  => sub {
         my ($pid, $status) = @_;
         warn "pid $pid exited with status $status";
+        $done->broadcast;
      },
   );
+  # do something else, then wait for process exit
+  $done->wait;
 =head2 CONDITION VARIABLES
 Condition variables can be created by calling the C<< AnyEvent->condvar >>
 method without any arguments.
    AnyEvent::Impl::CoroEV    based on Coro::EV, best choice.
    AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
    AnyEvent::Impl::EV        based on EV (an interface to libev, best choice).
    AnyEvent::Impl::Event     based on Event, second best choice.
    AnyEvent::Impl::Glib      based on Glib, third-best choice.
+   AnyEvent::Impl::Perl      pure-perl implementation, inefficient but portable.
    AnyEvent::Impl::Tk        based on Tk, very bad choice.
-   AnyEvent::Impl::Perl      pure-perl implementation, inefficient but portable.
    AnyEvent::Impl::Qt        based on Qt, cannot be autoprobed (see its docs).
    AnyEvent::Impl::EventLib  based on Event::Lib, leaks memory and worse.
    AnyEvent::Impl::POE       based on POE, not generic enough for full support.
 There is no support for WxWidgets, as WxWidgets has no support for
 =back
 =head1 EXAMPLE PROGRAM
-The following program uses an IO watcher to read data from STDIN, a timer
+The following program uses an I/O watcher to read data from STDIN, a timer
 to display a message once per second, and a condition variable to quit the
 program when the user enters quit:
    use AnyEvent;
 To give you an idea of the performance and overheads that AnyEvent adds
 over the event loops themselves (and to give you an impression of the
 speed of various event loops), here is a benchmark of various supported
 event models natively and with anyevent. The benchmark creates a lot of
-timers (with a zero timeout) and io watchers (watching STDOUT, a pty, to
+timers (with a zero timeout) and I/O watchers (watching STDOUT, a pty, to
 become writable, which it is), lets them fire exactly once and destroys
 them again.
 Rewriting the benchmark to use many different sockets instead of using
-the same filehandle for all io watchers results in a much longer runtime
+the same filehandle for all I/O watchers results in a much longer runtime
 (socket creation is expensive), but qualitatively the same figures, so it
 was not used.
 =head2 Explanation of the columns
 =head2 Results
           name watchers bytes create invoke destroy comment
          EV/EV   400000   244   0.56   0.46    0.31 EV native interface
-        EV/Any   100000   610   3.52   0.91    0.75 EV + AnyEvent watchers
+        EV/Any   100000   244   2.50   0.46    0.29 EV + AnyEvent watchers
-    CoroEV/Any   100000   610   3.49   0.92    0.75 coroutines + Coro::Signal
+    CoroEV/Any   100000   244   2.49   0.44    0.29 coroutines + Coro::Signal
-      Perl/Any   100000   513   4.91   0.92    1.15 pure perl implementation
+      Perl/Any   100000   513   4.92   0.87    1.12 pure perl implementation
-   Event/Event    16000   523  28.05  21.38    0.86 Event native interface
+   Event/Event    16000   516  31.88  31.30    0.85 Event native interface
-     Event/Any    16000   943  34.43  20.48    1.39 Event + AnyEvent watchers
+     Event/Any    16000   936  39.17  33.63    1.43 Event + AnyEvent watchers
-      Glib/Any    16000  1357  96.99  12.55   55.51 quadratic behaviour
+      Glib/Any    16000  1357  98.22  12.41   54.00 quadratic behaviour
-        Tk/Any     2000  1855  27.01  66.61   14.03 SEGV with >> 2000 watchers
+        Tk/Any     2000  1860  26.97  67.98   14.00 SEGV with >> 2000 watchers
-     POE/Event     2000  6644 108.15 768.19   14.33 via POE::Loop::Event
+     POE/Event     2000  6644 108.64 736.02   14.73 via POE::Loop::Event
-    POE/Select     2000  6343  94.69 807.65  562.69 via POE::Loop::Select
+    POE/Select     2000  6343  94.13 809.12  565.96 via POE::Loop::Select
 =head2 Discussion
 The benchmark does I<not> measure scalability of the event loop very
 well. For example, a select-based event loop (such as the pure perl one)
 can never compete with an event loop that uses epoll when the number of
-file descriptors grows high. In this benchmark, only a single filehandle
+file descriptors grows high. In this benchmark, all events become ready at
-is used (although some of the AnyEvent adaptors dup() its file descriptor
+the same time, so select/poll-based implementations get an unnatural speed
-to worka round bugs).
+boost.
 C<EV> is the sole leader regarding speed and memory use, which are both
 maximal/minimal, respectively. Even when going through AnyEvent, there are
 only two event loops that use slightly less memory (the C<Event> module
 natively and the pure perl backend), and no faster event models, not even
 C<POE>, regardless of underlying event loop (wether using its pure perl
 select-based backend or the Event module) shows abysmal performance and
 memory usage: Watchers use almost 30 times as much memory as EV watchers,
 and 10 times as much memory as both Event or EV via AnyEvent. Watcher
-invocation is almost 700 times slower than with AnyEvent's pure perl
+invocation is almost 900 times slower than with AnyEvent's pure perl
 implementation. The design of the POE adaptor class in AnyEvent can not
 really account for this, as session creation overhead is small compared
 to execution of the state machine, which is coded pretty optimally within
 L<AnyEvent::Impl::POE>. POE simply seems to be abysmally slow.

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.77 by root, Fri Apr 25 09:00:37 2008 UTC vs. Revision 1.83 by root, Fri Apr 25 13:39:08 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.77 by root, Fri Apr 25 09:00:37 2008 UTC vs.
Revision 1.83 by root, Fri Apr 25 13:39:08 2008 UTC